[ https://issues.apache.org/jira/browse/DERBY-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-4750. ---------------------------- Closing, since fixes have long since appeared in the Latest Alpha Manuals. > 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 > Fix For: 10.11.0.0 > > Attachments: DERBY-4750-2.diff, DERBY-4750.diff, > rrefdeclaretemptable.html, 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.2#6252)