Description: ------------ To create a new record (MySQL) in which i'll put new data, i used to try the following syntax: $item = new DBO_MyDBObject(); $item->id = 0; //id is the key with auto_increment flag on $newid = $item->insert(); I have my own class which encapsulates DB_DataObject, and there's a class function (method nuevo()) in which i put the above code (more or less) returning the newly created primary key. I then redefine the methods when needed. But since i do not know the definition of the objects which will inherit this nuevo() method (id is standard and every table i create has its primary key named like that), i cannot state a field to be filled with initial data to insert. I just need EMPTY data, with an auto_incremented key written to this new record. This method used to work fine until DB_DataObject 1.3 i guess. Now it is broken. Is there any way you can fix this annoying behaviour?

can you try CVS - this might be fixed there.

Nope. No fix using CVS. But release 1.3 works fine.

ok -- needs further investigation..

Could not reproduce here. Can you download the test in CVS - (modify the dsn to connect to your test database. http://cvs.php.net/co.php/pear/DB_DataObject/tests/simple.phpt?r=1.10 php -r simple.phpt .... at the end the output looks like this.. CONNECT : USING CACHED CONNECTION QUERY : INSERT INTO testproxy2 (id ) VALUES ( 2 ) query : QUERY DONE IN 0.00072801113128662 seconds 1 : Clearing Cache for myproject_dataobject_testproxy2 2--GET--

This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on pear.php.net. In case this was a pear.php.net website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better. finally tracked this one down...

Certainly fixed. Just wanted to thank you for your work & time.