>>>>> "SK" == Shreyas Kaushik <[EMAIL PROTECTED]> writes:
SK> But turning off logging for recovery operations could hamper the
SK> implementation of Derby's version of aries algo. Also, if the log is
SK> not written to the disk and is maintianed elsewhere ( main memory ? )
SK> what do we do in case of hardware/CPU crash how does recovery happen ?
SK> We'll have to have an architecture of failover, is that a good idea
SK> for Derby ?
It is a bit unclear from the report whether the submitter needsss to
be able to recover from failures. If the application only uses the
database for temporary data, it may be OK to start with a fresh
database.
The submitter says "he never use rollback" and think that he does not
need logging. I am not sure he really means that it is OK for the
database to become inconsistent should something unforeseen happen
that make it impossible to commit a transaction (e.g., full disk).
--
�ystein
