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

["Kim Haase (JIRA)" <ji...@apache.org>]

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

Kim Haase updated DERBY-4750:
-----------------------------

    Attachment: rrefdeclaretemptable.html
                DERBY-4750.diff

Mike, I apologize for taking 3 1/2 years to get to this! I am gradually finding time to work on older issues that seem still current and worth fixing. 

I'm attaching DERBY-4750.diff and rrefdeclaretemptable.html, which I hope follow your instructions correctly. Please let me know if further changes are needed.

M       src/ref/rrefdeclaretemptable.dita

Thanks very much.

> 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.4#6159)