Yes. When you create a temp. table, you can ask for the rows to be PRESERVED or DELETED at the transaction boundary. Since temp. tables are typically used for short duration (with in the same connection), hopefully they can do without compressing... (in the short term)
http://db.apache.org/derby/docs/10.1/ref/rrefdeclaretemptable.html Satheesh Mike Matrigali wrote: > Can Derby temp tables span transactions? > > Øystein Grøvlen wrote: > >>>>>>> "SB(" == Satheesh Bandaram (JIRA) <[email protected]> writes: >>>>>> >> >> >> SB(> [ >> http://issues.apache.org/jira/browse/DERBY-720?page=comments#action_12358063 >> ] SB(> Satheesh Bandaram commented on DERBY-720: >> SB(> ----------------------------------------- >> >> SB(> I think Derby shouldn't allow compress on synonyms... >> Synonym usage is valid only in DML operations. If no one objects, I >> can make compress ignore synonyms, like views. While I am there, I >> can also make it ignore temp. tables... This may be a good (short >> term) solution. >> >> SB(> I will also mark Derby-365 a duplicate of this bug. >> >> I my opinion, it is seldom a good idea to ignore an operation. Either >> one should execute the operation or the caller should be told (usually >> by an exception) than this operation will not be performed. >> > > >
