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

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Mike Matrigali
• Created: 20/Jul/10 22:02
• Updated: 14/Jul/14 14:59
• Resolved: 14/Jan/14 14:33

Description

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.