you very much again,
Best regards,
Samuel
- Original Message
From: Pavel Ivanov
To: General Discussion of SQLite Database
Sent: Thu, February 4, 2010 3:54:33 PM
Subject: Re: [sqlite] When incremental write is committed to the hard drive?
> commit = 1;
> pStmt != NULL
>
red
> and pending. At the same time sqlite3_sql(pStmt) says that that statement is
> a NULL statement.
>
> I just got more confused.
>
> Best regards,
> Samuel
>
>
> - Original Message
> From: Pavel Ivanov
> To: General Discussion of SQLite Database
> Se
u, February 4, 2010 2:07:12 PM
Subject: Re: [sqlite] When incremental write is committed to the hard drive?
> 1) What else can prevent incremental data to be written to the hard drive?
Besides all that I mentioned only explicit BEGIN statement can open
transaction and thus prevent anything a
> 1) What else can prevent incremental data to be written to the hard drive?
Besides all that I mentioned only explicit BEGIN statement can open
transaction and thus prevent anything after that from being written to
disk immediately until COMMIT is executed. What you can do now is
first of all use
Pavel,
Thank you very much for your email. I greatly appreciate
your knowledge on the internal workings of Sqlite and your kindness to share
it.
>All incremental writing is committed (and thus is written to disk)
>when blob handle is closed. And even when you close the handle
>transaction is com
All incremental writing is committed (and thus is written to disk)
when blob handle is closed. And even when you close the handle
transaction is committed only when there's no more blob handles or
SELECT statements open at the moment on the same connection.
Pavel
On Wed, Feb 3, 2010 at 7:41 PM, a
I use UPDATE for text columns in the table and any changes are committed to the
hard drive right away (well,
after about 120 ms).
This can be verified by using external tool. I use SQLite Manager to 'see' the
changes.
I use also sqlite3_blob_write(ppBlob,dataToWrite,dataCount,offsetInTheB
7 matches
Mail list logo
