Posted by Sam on 11/22/07 17:43

Here's how I understand the situation right now:
Non-MySQL DBs use DB's nextId() and createSequence(). The sequence
info for DB says that you should only use these methods to access the
sequences, including for creation. I had used serials as data type for
my ids however, which results in a sequence automatically being
created by the DB. So I thought this could have caused some confusion.
So I removed the default value for the id in the table and got rid of
the sequence it was using as well. Now insert fails completely because
it tries to insert a NULL value into the id column. So it seems that
DB_DataObject doesn't manage to get an id at all right now.
Anyone have this working?

• Next in forum: Re: location finder by typing your post code (UK)
• Prev in forum: Re: mail() - message lines <= 70 chars
• Thread view: Re: Returning the id of an inserted row when using DB_DataObject->insert() with postgresql

[Reply to this message]