[
https://issues.apache.org/jira/browse/DERBY-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601789#action_12601789
]
Dag H. Wanvik commented on DERBY-3687:
--------------------------------------
I see there are tests in SavepointJDBC30Test.java, cases #17, #18 and #19 and
#48, which
test various (illegal) nesting scenarios:
- testNoNestedSavepointsWhenUsingSQL (SQL inside SQL)
- testNoNestedSavepointsInsideJdbcSavepoint (JDBC inside SQL)
- testNoNestedSavepointsInsideSqlSavepoint (SQL inside SQL)
- xtestNestedSavepoints (SQL inside JDBC; not enabled, cf. x in fixture name ?)
I can understand why it is wise to avoid mixing the two savepoint kinds, but
can someone enlighten me as to the rationale for not allowing nesting of SQL
savepoints? (keeping in mind that the standard doesn't dictate this; is this
some kind of compatibility decision?)
> Make client driver allow nested savepoints
> ------------------------------------------
>
> Key: DERBY-3687
> URL: https://issues.apache.org/jira/browse/DERBY-3687
> Project: Derby
> Issue Type: Improvement
> Components: Network Client
> Reporter: Dag H. Wanvik
> Attachments: Main.java
>
>
> Currently, only the embedded driver allows nested savepoints, cf. the
> attached repro.
> In the interest of harmonizing the drivers it would be nice to make the
> client driver allow this as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
