Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

2004-09-07 Thread Guillaume Fougnies
Tue, Sep 07, 2004 at 12:59:37PM +0100: Christian Smith wrote: > On Tue, 7 Sep 2004, Guillaume Fougnies wrote: > > >Mon, Sep 06, 2004 at 11:56:21PM -0700: Darren Duncan wrote: > >> > >> What you probably saw with the 3ms is the time between when you > >> issued the insert command and when control

Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

2004-09-07 Thread D. Richard Hipp
George Ionescu wrote: > > If the database becomes corrupted after a power failure while inserting > records, is there any way of repairing the database? > No. -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565

Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

2004-09-07 Thread Guillaume Fougnies
Mon, Sep 06, 2004 at 11:56:21PM -0700: Darren Duncan wrote: > At 9:20 AM +0300 9/7/04, George Ionescu wrote: > >as Nuno Lucas suggested, I've tried inserting one record using > >synchronous = OFF. That makes a *huge* difference: 150 ms > >(synchronous=FULL) vs. 3 ms (synchronous=OFF) !! So I'm

Re: [sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

2004-09-07 Thread Darren Duncan
At 9:20 AM +0300 9/7/04, George Ionescu wrote: as Nuno Lucas suggested, I've tried inserting one record using synchronous = OFF. That makes a *huge* difference: 150 ms (synchronous=FULL) vs. 3 ms (synchronous=OFF) !! So I'm asking this: anyone has had any real-word experience with multi-user

[sqlite] Risks involved with using synchronous=OFF (was 'Single INSERT is very slow')

2004-09-07 Thread George Ionescu
Hello sqlite users, Hello dr. Hipp, as Nuno Lucas suggested, I've tried inserting one record using synchronous = OFF. That makes a *huge* difference: 150 ms (synchronous=FULL) vs. 3 ms (synchronous=OFF) !! So I'm asking this: anyone has had any real-word experience with multi-user access and