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 "Kim Haase (JIRA)" <ji...@apache.org> on 2008/05/23 19:27:55 UTC

[jira] Created: (DERBY-3691) Reference Manual missing information on transaction-related statements

Reference Manual missing information on transaction-related statements
----------------------------------------------------------------------

                 Key: DERBY-3691
                 URL: https://issues.apache.org/jira/browse/DERBY-3691
             Project: Derby
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 10.4.1.3
            Reporter: Kim Haase
            Priority: Minor


The Derby Reference Manual does not currently document the following statements:

SAVEPOINT
RELEASE
COMMIT
ROLLBACK

Were they omitted deliberately in order to encourage people to use JDBC for transaction-related work? If not, shouldn't they be added?


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


[jira] Commented: (DERBY-3691) Reference Manual missing information on transaction-related statements

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603560#action_12603560 ] 

Knut Anders Hatlen commented on DERBY-3691:
-------------------------------------------

COMMIT and ROLLBACK are not part of Derby's SQL syntax, but ij understands them and translates them to the corresponding JDBC calls. These commands are documented in the Tools and Utilities Guide.

ROLLBACK TO SAVEPOINT, SAVEPOINT and RELEASE SAVEPOINT are part of Derby's SQL, and they are also part of the SQL standard, so I think it's a good idea to document them in the Reference Manual.

> Reference Manual missing information on transaction-related statements
> ----------------------------------------------------------------------
>
>                 Key: DERBY-3691
>                 URL: https://issues.apache.org/jira/browse/DERBY-3691
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.4.1.3
>            Reporter: Kim Haase
>            Priority: Minor
>
> The Derby Reference Manual does not currently document the following statements:
> SAVEPOINT
> RELEASE
> COMMIT
> ROLLBACK
> Were they omitted deliberately in order to encourage people to use JDBC for transaction-related work? If not, shouldn't they be added?

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


[jira] Commented: (DERBY-3691) Reference Manual missing information on transaction-related statements

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603582#action_12603582 ] 

Dag H. Wanvik commented on DERBY-3691:
--------------------------------------

+1

But see my unresolved questions under DERBY-3687. The answer may or may not pertain to why this is presently undocumented. I still think we should document it, though.

> Reference Manual missing information on transaction-related statements
> ----------------------------------------------------------------------
>
>                 Key: DERBY-3691
>                 URL: https://issues.apache.org/jira/browse/DERBY-3691
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.4.1.3
>            Reporter: Kim Haase
>            Priority: Minor
>
> The Derby Reference Manual does not currently document the following statements:
> SAVEPOINT
> RELEASE
> COMMIT
> ROLLBACK
> Were they omitted deliberately in order to encourage people to use JDBC for transaction-related work? If not, shouldn't they be added?

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