[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lost INSERTs
- To: mckoidb@xxxxxxxxx
- Subject: Re: Lost INSERTs
- From: Tobias Downer <toby@xxxxxxxxx>
- Date: Wed, 01 Jan 2003 12:12:07 -0800
- Delivered-To: mailing list mckoidb@mckoi.com
- Mailing-List: contact mckoidb-help@mckoi.com; run by ezmlm
- References: <F1223xsKzIPLmPIei5g000197bd@hotmail.com>
- User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1a) Gecko/20020611
Thank you Fred. I'll look into it.
Toby.
Fred Santos wrote:
>
> Hi Toby.
>
> A while ago I reported that I'm experiencing data loss
> when AutoCommit is set to false. I'm now able to reproduce the
> problem using the attached test application.
>
> The issue is that INSERTs get lost when all three
> conditions hold true:
>
> 1 AutoCommit it set to false on the connection
> 2 The database is stopped after the INSERT operation,
> and then restarted
> 3 The database is compacted through "COMPACT TABLE" (!)
>
> The application works correctly if I don't perform
> the "COMPACT TABLE".
> Also, if AutoCommit is set to true, the application
> works correctly irrespective of whether the DB is compacted or not.
>
> So it's the combination of setAutoCommit(false) and
> COMPACT TABLE which leads to an INSERTed record to disappear
> when the database is restarted. Even though I'm calling
> commit on the connection before I shut down the database.
>
> Anyway, please have a look at the included test application.
> The database needs to be deleted before you start the test.
> To trigger the problem, un-comment the call to
> testCase.compactDatabase() located in main.
>
> Configuration: McKoi0.94h, JDK 1.4.1_01, Win2000 SP2
>
> Regards,
>
> Fred