No, I have none of the below...
It was my own stupid mistake...
I was like "SELECT MAX(ID) FROM table"
and then I was like ... Mmmm, start again from that max-id... Of course if it is already in the database it has already been reworked... So I had to do +1 :p
Thx & sorry for the timewaste
At 22:50 3/11/2004, you wrote:
On 11/03/2004 08:48 PM, Reid Thompson wrote:
> [EMAIL PROTECTED] wrote:
>
>>In a message dated 11/3/2004 12:20:36 PM Eastern Standard Time,
>>[EMAIL PROTECTED] writes:
>>
>>How can I make sure after an insert that everything has been flushed
>>to disc?
>>
>>I mean, I want even my program to become slower as long as I know
>> everything have been written to disc.
>>
>>At the moment I am using:
>>PRAGMA default_synchronous = FULL;
>>PRAGMA synchronous = FULL;
>>
>>
>>And the queries are all INSERT's without a transaction.
>>
>>
>>Thx,
>>
>>KaReL (aka Steven)
>>
>>Main Webpage : _http://www.karels0ft.be/
>>_ (http://www.karels0ft.be/) ICQ # : 35217584
>>
>>
>>
>>If synchronus=FULL is set. every insert without a transaction is
>>flushed to disk before sqlite3_finalized is returned. You are safe.
>>
>>Wei
>
>
> Unless you are using IDE disks that respond that they've written to the
> disk when in fact they have not.
..or you have some transaction-based/journaling filesystem which delays
data writing to disk ;-)
> reid
>
>
--
Konstantin Malakhanov <[EMAIL PROTECTED]>
KaReL (aka Steven)
Main Webpage : http://www.karels0ft.be/
ICQ # : 35217584
pgpBcc6OJc9WT.pgp
Description: PGP signature
