db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3579) The Developer's Guide incorrectly describes the behavior of transactions inside procedures and functions
Date Wed, 23 Jul 2008 22:14:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase updated DERBY-3579:

    Attachment: DERBY-3579-3.zip

Thanks very much, Rick, for catching those problems.

I think the first file you meant was cdevconcepts29416.dita (Using auto-commit). I made the
changes you suggested there and fixed the typo in cdevconcepts36881.dita. 

I'm attaching DERBY-3579-3.diff and DERBY-3579-3.zip. Please let me know if further changes
are needed.

> The Developer's Guide incorrectly describes the behavior of transactions inside procedures
and functions
> --------------------------------------------------------------------------------------------------------
>                 Key: DERBY-3579
>                 URL: https://issues.apache.org/jira/browse/DERBY-3579
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-3579-2.diff, DERBY-3579-2.stat, DERBY-3579-2.zip, DERBY-3579-3.diff,
DERBY-3579-3.zip, DERBY-3579.diff, DERBY-3579.zip, z.java
> The "Programming database-side JDBC procedures" section of the Developer's Guide misleads
users about how transactions can be managed inside database procedures. For instance, the
section titled "Invoking a procedure using the CALL command" says the following: "Procedures
that use nested connections, on the other hand, are not permitted to commit or roll back and
can therefore be rolled back after the calling statement." This is not true. User-coded procedures
can issue both commit() and rollback() on the nested connection bound to the "jdbc:default:connection"
URL and those methods have the desired behavior. The whole "Programming database-side JDBC
procedures" section could use an overhaul since it appears to make other misleading statements
about the behavior of transactions inside routines. Thanks to Dag for pointing out the following
email thread: http://www.nabble.com/Transaction-Problems-of-a-Derby-Stored-Procedure-td15494178.html

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message