Hi,
Yes they are.
With "PRAGMA wal_checkpoint" it works as expected.
Yoni.
On Tue, Aug 10, 2010 at 2:50 PM, Dan Kennedy wrote:
>
> On Aug 10, 2010, at 6:03 PM, Yoni Londner wrote:
>
> > Hi,
> > Yes, it explains allot.
> > But, according to you, the following program should work.
> > I don't use
On Aug 10, 2010, at 6:03 PM, Yoni Londner wrote:
> Hi,
> Yes, it explains allot.
> But, according to you, the following program should work.
> I don't use transactions, shared cache or threads.
> Just run the checkpoint from another connection.
> And still - WAL file is getting bigger and bigger
Hi,
Yes, it explains allot.
But, according to you, the following program should work.
I don't use transactions, shared cache or threads.
Just run the checkpoint from another connection.
And still - WAL file is getting bigger and bigger without limit.
If I do the checkpoint with the same connection,
> Hi,
> I just wanted to add that I changed the program a little bit to not
> use
> transactions and threads, and I still get the same problem (huge WAL
> file).
> All I do is endless loop of insert, and every X insert, I perform a
> checkpoint on another sqlite connection (but in the same th
Hi,
I just wanted to add that I changed the program a little bit to not use
transactions and threads, and I still get the same problem (huge WAL file).
All I do is endless loop of insert, and every X insert, I perform a
checkpoint on another sqlite connection (but in the same thread).
It only worke
Hi Richard,
Thanks for the quick response.
I wrote a little program that demonstrate the error (below).
It opens a new DB, create a table, and start an endless loop of INSERT's.
In a background thread it performs a wal checkpoint.
There is no difference in WAL file size - with or without transactio
On Tue, Aug 10, 2010 at 2:24 AM, Yoni Londner wrote:
> Hello,
> I have a questions about the correct use of transactions and WAL.
>
> I am writing an application that:
> 1. should very fast
> 2. should be very responsive
> 3. don't care if the last N minutes of data will be lost (but DB should
Hello,
I have a questions about the correct use of transactions and WAL.
I am writing an application that:
1. should very fast
2. should be very responsive
3. don't care if the last N minutes of data will be lost (but DB should
never be corrupted)
What I tried to do:
1. open a transaction
8 matches
Mail list logo