On Thu, 22 Apr 2004 [EMAIL PROTECTED] wrote:Look at the message you quoted from - it was an update to http://wiki.apache.org/db-torque/PostgreSQLFAQ rather than the obsolete page you reference here (I have just updated all of the old wiki pages to point to the new wiki).
+== When I examine the source code I see that the PostgreSQL currval()
function is used for idMethod='native' - this cannot possibly be right
since it should quite obviously be using nextval(). == + +Please read
the following thread in its entirety: + *
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=3537
+The source also gives the impression that it is somehow using
AUTOINCREMENT when SEQUENCE would seem to be the more obvious choice. This is more of an indication of whether or not the id should be
returned before or after the insert - the names of these things could
certainly be improved. +
== Do I need to patch the PostgreSQL driver to work with Torque? ==
Thankyou. I see that this problem has been encountered before.
So now if I don't set the id-method-parameter seqName, then postgres fails because it's trying to select currval from a sequence which noone has selected nextval from.
And if I do set the id-method-parameter seqName, then postgres fails because it tries to create tables with a primary key sequence that Torque already created.
It looks rather like Hobson's choice, and it's documented as such at http://nagoya.apache.org/wiki/apachewiki.cgi?TorqueProjectPages/PostgreSQLFAQ
Are you, by any chance, using a really old [and obsolete] version of7.3.4 - not cutting edge, but by no means old. If you go to the page I reference above and read the FAQ you will save yourself a bunch of time.
postgres?
I won't say "You were right" because out of the box, it doesn't work, andI am not looking for you to acknowledge that I am right, just attempting to jump to the conclusion (that it works) without covering the same old stuff. Yes, there are a few small issues with PostgreSQL support in Torque. I am reasonably comfortable that most of the issues are documented on the FAQ page and that none of these are show stoppers.
can't be made to work without hacking the generated code. However, I will
happily admit that it wasn't the bug I first thought it was.
Scott
-- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
