Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <1899156903.1124233794580.JavaMail.jira@ajax.apache.org>
Date: Wed, 17 Aug 2005 01:09:54 +0200 (CEST)
From: "Mike Matrigali (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-150) Disable transaction logging
In-Reply-To: <860460619.1108968408627.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-150?page=all ]

Mike Matrigali updated DERBY-150:
---------------------------------

      Component: Store
        Summary: Disable transaction logging  (was: Disable logging)
    Description: 
As a means of improving performance, I would like to be able to disable logging completely.

I use Derby in applications thatnever use rollback and I suspect that quite a lot of time is going to logging.

Thanks

  was:
As a means of improving performance, I would like to be able to disable logging completely.

I use Derby in applications thatnever use rollback and I suspect that quite a lot of time is going to logging.

Thanks


Note that even if your application does not  explicitlly call rollback many internal operations in derby 
use rollback , like: lock timeout, lock deadlock, statement errors, server crash.

If such a feature were provided what would you expect from the database if the machine crashed:
1) no database expected after crash
2) a bootable database that would have inconsistent data (ie. partial data from a transaction)
3) a consistent database from some arbitrary point in time.

> Disable transaction logging
> ---------------------------
>
>          Key: DERBY-150
>          URL: http://issues.apache.org/jira/browse/DERBY-150
>      Project: Derby
>         Type: New Feature
>   Components: Store
>  Environment: all
>     Reporter: Barnet Wagman

>
> As a means of improving performance, I would like to be able to disable logging completely.
> I use Derby in applications thatnever use rollback and I suspect that quite a lot of time is going to logging.
> Thanks

-- 
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