db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-218) Add Relaxed Durability option
Date Mon, 23 May 2005 03:11:57 GMT
     [ http://issues.apache.org/jira/browse/DERBY-218?page=all ]
     
Sunitha Kambhampati closed DERBY-218:
-------------------------------------


> Add Relaxed Durability option
> -----------------------------
>
>          Key: DERBY-218
>          URL: http://issues.apache.org/jira/browse/DERBY-218
>      Project: Derby
>         Type: Improvement
>   Components: Store
>     Versions: 10.1.0.0
>  Environment: all
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>      Fix For: 10.1.0.0

>
> Dan Debrunner posted a fix to allow for relaxed durability changes in http://article.gmane.org/gmane.comp.apache.db.derby.user/681/match=relaxed+durability
> 1) Need to add this option in Derby maybe as some property
> 2) Also from discussions on the list, Mike suggested that 
> - that the logging system be changed to somehow
> record that the database has operated in this manner, so that if
> the database goes corrupt we don't waste effort trying to figure out
> what when wrong.  Probably need some way to mark the log records, the
> log control file and write a message to the user error log file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message