[jira] [Commented] (DERBY-4750) add documentation to declare global temporary tables to explain expected behavior when used with XA transactions.

["Rick Hillegas (JIRA)" <ji...@apache.org>]

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

Rick Hillegas commented on DERBY-4750:
--------------------------------------

Hi Kim,

The DERBY-4750.diff change looks good to me. For completeness sake, I think it's worth saying explicitly, as Mike suggested, that the temporary table is dropped when the XA transaction commits or aborts. Thanks.

> add documentation to declare global temporary tables to explain expected behavior when used with XA transactions.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4750
>                 URL: https://issues.apache.org/jira/browse/DERBY-4750
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.7.1.1
>            Reporter: Mike Matrigali
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-4750.diff, rrefdeclaretemptable.html
>
>
> Add the following information to the DECLARED GLOBAL TEMPORARY TABLE documentation, probably in the restrictions section.
> Declared Global Temporary Tables can be used in XA transactions, but
> can only be declared and accessed within the scope of a single XA transaction.
> Derby only can support access to the table until one of the following XA
> interfaces is called:
>   XAResource.end(), XAresource().prepare(), or XAResource.commit()
> Derby will automatically drop the temporary table whenever the XA tranaction
> commits or aborts, subsequent attempts to access the tables will encounter
> table not found errors.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)