@Jay:
Thanks for the official information.
>You'll see the slow down anytime you access anything "past" the BLOB.
>To avoid that, put the BLOBs at the end of the rows and avoid "SELECT *" style
>queries.
Yes this is exactly what I found.. The problem with putting them at the end of
the table
On Sat, 29 Jan 2011 15:07:47 -0800 (PST)
Rael Bauer wrote:
> It seemed strange that a simple "select * from table" that I was
> doing was so slow. The table contained about 20 columns (fields) and
> 300 rows. The select took about 1.5 seconds. (using SQLite Expert).
>
> So
>It seemed strange that a simple "select * from table" that I was doing
>was so slow. The table contained about 20 columns (fields) and 300
>rows. The select took about 1.5 seconds. (using SQLite Expert).
Does the run time settle at 1.5 s after a few runs or is that a
first-run time ?
As an
On 30 Jan 2011, at 2:16am, Jay A. Kreibich wrote:
> You'll see the slow down anytime you access anything "past" the BLOB.
> To avoid that, put the BLOBs at the end of the rows and avoid "SELECT *"
> style queries.
Avoiding 'SELECT *' unless you actually want * is good advice in any case.
On Sat, Jan 29, 2011 at 03:07:47PM -0800, Rael Bauer scratched on the wall:
> It seemed strange that a simple "select * from table" that I was
> doing was so slow. The table contained about 20 columns (fields)
> and 300 rows. The select took about 1.5 seconds. (using SQLite Expert).
> So my
On Saturday, January 29, 2011 at 5:54 PM, Rael Bauer wrote:
> The table contains an id field with a unique index and another field with a
> non-unique index.
>
>
> > So you got about 40 Meg of data in 1.5 seconds. Use your OS's copy command
> > (or some graphical equivalent) to duplicate
The table contains an id field with a unique index and another field with a
non-unique index.
>So you got about 40 Meg of data in 1.5 seconds. Use your OS's copy command
>(or some graphical equivalent) to duplicate that file. How long does it take
>?
You seemed to miss what I was saying:
On 29 Jan 2011, at 11:07pm, Rael Bauer wrote:
> It seemed strange that a simple "select * from table" that I was doing was so
> slow. The table contained about 20 columns (fields) and 300 rows. The select
> took about 1.5 seconds. (using SQLite Expert).
Do you have an indexes or UNIQUE
It seemed strange that a simple "select * from table" that I was doing was so
slow. The table contained about 20 columns (fields) and 300 rows. The select
took about 1.5 seconds. (using SQLite Expert).
The table contained a blob field, with a "fair" amount of data spread over the
rows (max was
9 matches
Mail list logo