db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5161) Cannot rollback after syntax error in internal statement
Date Tue, 29 Mar 2011 12:47:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012462#comment-13012462

Dag H. Wanvik commented on DERBY-5161:

So, this explains the hang I saw in DERBY-5157 with the new test cases present and the code
changes backed out. Looks like a good fix to me if regressions pass. Although we should not
normally see syntax errors in internal statements, its good that
the error handling is correct if it ever happens.


> Cannot rollback after syntax error in internal statement
> --------------------------------------------------------
>                 Key: DERBY-5161
>                 URL: https://issues.apache.org/jira/browse/DERBY-5161
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: finally.diff
> To reproduce, execute the statements below in ij. Can only be reproduced this way before
DERBY-5157. I don't know how to reproduce it when that bug is fixed.
> ij version 10.7
> ij> connect 'jdbc:derby:db;create=true';
> ij> autocommit off;
> ij> create table t(x int);
> 0 rows inserted/updated/deleted
> ij> alter table t add column """" int default 42;
> ERROR 42X01: Syntax error: Encountered "\"" at line 1, column 22.
> Issue the 'help' command for general information on IJ command syntax.
> Any unrecognized commands are treated as potential SQL commands and executed directly.
> Consult your DBMS server reference documentation for details of the SQL syntax supported
by your server.
> ij> rollback;
> ERROR X0Y67: Cannot issue rollback in a nested connection when there is a pending operation
in the parent connection.
> The error message implies that we've called rollback() on a nested transaction, whereas
we're in fact called it on the parent transaction.
> Expected result: The rollback statement should abort the transaction without raising
any errors.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message