db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Created: (DERBY-218) Add Relaxed Durability option
Date Thu, 14 Apr 2005 16:40:46 GMT
thanks for the example.  It seems like providing some sort of
temporary table which is not logged would also help those applications.
I think derby already does this if the temp tables are single user -
single transaction, but no multi-user cross transaction temp table support.

Unlogged multi-user temporary tables might be interesting.  I believe
there is a SQL standard in this area.  Anyone know what other db's do
in this area?

RPost wrote:
>>Dibyendu Majumdar wrote:
>>From: "Mike Matrigali" <mikem_app@sbcglobal.net>
>>
>>> From responses to Dan's original post on building a system with the
>>>sync options disabled it seemed like there was enough response that
>>>those options should be made available.  I admit I am worried because
>>>this system can no longer guarantee recoverability.  It would be
>>>interesting to know how people would use such a configuration.
>>
>>I agree with you that a database system without recoverability is useless.
> 
> 
> One use for a database without recoverability is for data
> warehousing/reporting.
> 
> The database used as a datamart needs to be created without error but once
> created the core tables can be read-only. Other read/write tables will be
> used for searches, match-engine results and temporary tables to support
> report-ready processes. Loss of data in these tables would not be serious
> since they start out empty at the start of a process anyway.
> 
> 
> 


Mime
View raw message