Eric,
Thanks for the quick response.
> Sounds to me like the matching rows are located near the beginning of
> the table's physical storage, so you get them quickly, and then the next
> sqlite3_step() has to scan the rest of the table.
An idea worth testing, but using the official sqlite3 console
Carl Jacobs wrote:
Hello, I'm a new user to this group as I haven't had any issues with sqlite
till now. I tried searching to see if this question has been asked before,
but couldn't find anything.
I'm using Windows.
I have a table with ~45 colums and ~17000 records. I do a search for some
stuf
Hello, I'm a new user to this group as I haven't had any issues with sqlite
till now. I tried searching to see if this question has been asked before,
but couldn't find anything.
I'm using Windows.
I have a table with ~45 colums and ~17000 records. I do a search for some
stuff using 'SELECT * FR
3 matches
Mail list logo