Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 3:15 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [sqlite] RE: SQLite performance with mid-size databases
Richard,
I notice you don't seem to be getting useful replies
"Ismail Kizir" <[EMAIL PROTECTED]>
17/06/2004 06:48 PM
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: [sqlite] RE: SQLite performance with mid-size databases
> I had the same problem as Richard's.
> Unfortunately, i have decided to u
Jacob Engstrand wrote:
>
> On 2004-06-17, at 16.39, [EMAIL PROTECTED] wrote:
>
>> If you have a large record size, then it also helps tremendously to put the
>> indexed columns first in the row (I had a table with large blob data that
>> was terribly slow to query until I moved the small,
On 2004-06-17, at 16.39, [EMAIL PROTECTED] wrote:
If you have a large record size, then it also helps tremendously to
put the
indexed columns first in the row (I had a table with large blob data
that
was terribly slow to query until I moved the small, non-blob columns
first).
[That was found
Ionut,
Thank you for your input. Do you mean precompilation and then
subsequent calls to the sqlite_bind API?
Am definitely using transactions, and the database is entirely read-only
with only the client in question accessing the db.
The poor and linearly scaling performance degradation with
5 matches
Mail list logo
