You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/07/09 02:08:30 UTC

[jira] Commented: (DERBY-1208) Attempts to reuse a prepared statement after an execution-time error causes ASSERT failure in SANE mode, but work fine in INSANE.

    [ http://issues.apache.org/jira/browse/DERBY-1208?page=comments#action_12419892 ] 

Kathey Marsden commented on DERBY-1208:
---------------------------------------

Thanks HÃ¥vard  for the patch and the test. It is especially good  that we will now have coverage for failures during  this part of execution.

Your approach looks good to me. I ran the test and verified the original repro  fails without your patch and passes with it.

I wouldn't normally commit in this area but the patch looks pretty harmless, so if nobody objects, I  will run derbyall and then commit Monday.  It would be good if someone familiar with the SQL area also took a quick look.


Kathey


> 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: 1208.diff, 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