Description: ------------ I don't claim to understand the SQL query in the getSequenceName method, but I do know that it can return incorrect results. Running that query directly on my server returns two rows. 1: schema.table_field_seq 2: table_field_seq The first result is being returned by the method, when the second field is the needed result. I have identical tables in different schemas, and this method is returning the wrong schema! You need to eliminate the first result somehow, as the schema should be determined solely by the schema search path (which I do have set in my application).

Can you post a script that shows what you experience?

Here you go. This errors for me, rather than returning the lastInsertId. <?php /* DATABASE CREATION CREATE DATABASE test; CREATE SCHEMA schema1; CREATE SCHEMA schema2; CREATE SCHEMA schema3; CREATE TABLE schema1.mytable ( id SERIAL PRIMARY KEY, value TEXT ); CREATE TABLE schema2.mytable ( id SERIAL PRIMARY KEY, value TEXT ); CREATE TABLE schema3.mytable ( id SERIAL PRIMARY KEY, value TEXT ); */ require_once 'MDB2.php'; $username = ''; $password = ''; $dsn = "pgsql://$username:$password@unix(/tmp/)/test"; $options = array(); $mdb2 =& MDB2::connect($dsn, $options); if (PEAR::isError($mdb2)) { die($mdb2->getMessage()); } /** * schema2 is important... it will not be the first result * returned by getSequenceName */ $res =& $mdb2->query('SET search_path to schema2, public'); if (PEAR::isError($res)) { die($res->getMessage()); } $sql = "INSERT INTO mytable (value) VALUES ('value')"; $affected =& $mdb2->exec($sql); if (PEAR::isError($affected)) { die($affected->getMessage()); } $id = $mdb2->lastInsertId('mytable', 'id'); if (PEAR::isError($id)) { echo "<pre>"; print_r($id); exit; } echo $id; ?>

Another bug in getSequenceName: list($table, $field) = explode('_', $sqn); will not return the correct $table and $field if either (or both) have an underscore in them, i.e. "my_table", "table_id".

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.