I had been struggling with some weirdness that CakePHP has been displaying while trying to add some new features to the baseball league website, where Cake + PHP 4.4 + Postgres were deciding to just be sulky and not work together well.

Lucky for me, it turns out that the solution (for now) to the problem was to simply add the name of the sequence for that table as a variable to the model definition.

He includes the code for the Model that creates the connections between hos tables (belongsTo) and creates a sequence global to the class - note the naming convention.

Last week we left off with an example where notice, exception and log levels are sent to the client. This week we present more POSTGRES exception examples, and continue with our article on Postgres exception handling.

They create a few examples:

• handling other error conditions with OTHERS
• using f_ex2
• returning NO_DATA_FOUND and TOO_MANY_ROWS
• handling exceptions like table constraints
• nested exceptions
• using f_ex5
• a RAISE EXCEPTION dilemma
• using f_ext1

Postgres exceptions are quite different from PHP exceptions; whereas PHP 5 uses the traditional "Try And Catch" format, Postgres exceptions can only be defined, executed and processed inside the body of the function that triggered the exception.

The phpPgAdmin Team is proud to announce a new major release of phpPgAdmin. Version 4.1 adds many new features, bug fixes and updated translations over the previous version.

Updates include:

• New icons by Niko , from the graphics repository on pgFoundry
• Send encrypted passwords over the wire wherever possible
• Display Prepared Transactions
• Add Support For IN/OUT Parameters