Hello,
I guess that there is a bug that causes the above exception (error
message "[-3102]: Invalid subtrans structure") when a row containing a
column of type LONG is updated. But it seems that this error is thrown
only under certain conditions.
- the exception occurs only if the value of the LONG-column is NOT NULL.
- the exception is thrown only when using a certain sequence of statements.
In our example the exception is thrown using the following sequence:
SELECT: we read the last row's primary key of that table
INSERT: we insert the new row containing some data for the column of
type LONG [prep.setBytes(byte[])]
UPDATE: we update the inserted row while all non-key columns are updated
(altough the byte[]-content remains the same)
-> If we place another SELECT-statement between the above INSERT and
UPDATE statement that reads the inserted row from the database, the
exception is *not* thrown.
-> Altough the exception is thrown, the update is done correctly in our
example
We use JDBC driver 7.6.0 Build 012-000-004-339 on MaxDB Kernel 7.5.0
Build 034-121-118-234
I found that there was a similar problem posted on 2003-03-03 and
possibly the same problem was the cause of this report:
http://lists.mysql.org/maxdb/19277 (28.11.2003)
Perhaps I'll be able to post a program/tabledefinition that can
reproduce the problem.
Best regards,
Gabriel Matter
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
