Is there a known problem using PostgreSQL native sequences with the decoupled torque 3.0 dev (CVS version from 2002-02-24) and postgres 7.2?
To make a long story short I had to make three one line changes to the postgres database adapter to get sequences working. What confuses me is that the original code seems to be blatantly wrong, like it has never been tested. The id method is set to auto increment (not sequence) and the use of the nextval and currval sequence functions is reversed. Thus back to my question, is this supposed to work somehow or is it known to be broken? Side note, I know that idBroker works, but I have an existing database and torque won't be the only thing inserting new rows. Other than boolean not working (next post) torque is working very well. My bytea and text columns worked right from the start, and I like the foreign key helper methods that torque adds. Thanks to all the torque developers for a nice OR mapping layer. Steve Stock [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
