bonjour,
Le vendredi 07 octobre 2005, Anhaus, Thomas a écrit...
> But you mentioned a problem with NEXTVAL. Is it possible, that a sequence
> that has been recreated is used inside your procedure ?
> If this is true and the sequence is accessed directly (i.e. without SQL) this
> would explain your problems.
May be. I use a sequence for my primary key (DEFAULT SERIAL).
My sequence problems came back, with a new table, and a new dbproc.
I have choosen to disable the use of the
cursor.execute("CALL DBPROC...") until a next version, replaced by
sdb.sql.sqlX("INSERT...VALUES...").getLastSerial()
The frame maxdb-htmldoc-76_670/23/1b8b79fb679a478d16c8526561efb2/content.htm
should be corrected : this page is talking about the sqlX() method, but
shows two examples using the sql() method with sqlX() parameters.
--
jm
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
