db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Satheesh Bandaram <sathe...@Sourcery.Org>
Subject Re: [jira] Commented: (DERBY-720) Calling SYSCS_INPLACE_COMPRESS_TABLE on a synonym or a temp table results in a NullPointerException
Date Mon, 21 Nov 2005 17:56:25 GMT
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) <derby-dev@db.apache.org>
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.
>>
>
>
>


Mime
View raw message