[ http://issues.apache.org/jira/browse/DERBY-1208?page=all ]
A B updated DERBY-1208:
-----------------------
Attachment: d1208.java
derby.log
Attaching a simple repro for this issue. To run against embedded mode, run:
> java d1208 embedded
I've also attached the derby.log file created from running the repro.
Against a SANE set of jars the output is:
----
Using driver: org.apache.derby.jdbc.EmbeddedDriver
Query 1 result set: 10, Row 1
Query 2 result set: 20, Row 2
Query 3 failed as expected: Attempt to divide by zero.
Query 4 failed: Java exception: 'ASSERT FAILED ProjectRestrictResultSet already
open: org.apache.der
by.shared.common.sanity.AssertFailure'.
Query 5 failed: Java exception: 'ASSERT FAILED ProjectRestrictResultSet already
open: org.apache.der
by.shared.common.sanity.AssertFailure'.
Database shutdown.
[ Done. ]
----
With INSANE jars, the output is:
----
Using driver: org.apache.derby.jdbc.EmbeddedDriver
Query 1 result set: 10, Row 1
Query 2 result set: 20, Row 2
Query 3 failed as expected: Attempt to divide by zero.
Query 4 result set: 40, Row 4
Query 5 result set: 50, Row 5
Database shutdown.
[ Done. ]
> Attempts to reuse a prepared statement after an execution-time error causes
> ASSERT failure in SANE mode, but work fine in INSANE.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1208
> URL: http://issues.apache.org/jira/browse/DERBY-1208
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: A B
> Priority: Minor
> Attachments: d1208.java, derby.log
>
> Please see the comments in DERBY-1196 for the discussion that prompted the
> filing of this issue. In short, if one attempts to reuse a prepared
> statement with a new set of parameters after a previous call to execute that
> statement has failed, the result will be an ASSERT failure in SANE mode.
> When the same thing is done in INSANE mode, everything works as one might
> expect it to.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
