Correcting a minor nit:
Igor Tandetnik wrote:
> Magnus Manske <[EMAIL PROTECTED]>
> wrote:
> The condition could be written a bit more laconically:
>
> pos1 BETWEEN 1 AND 100
>
>> On my table (ca. 180K entries) this takes about 10 seconds for the
>> above, which returns all rows.
>
> Since
Magnus Manske <[EMAIL PROTECTED]>
wrote:
> I've found the strangest issue today. I have a sqlite3 database that
> contains the following table:
>
> CREATE TABLE MAL9_single ( read_name VARCHAR[32], pos1 INTEGER, seq1
> VARCHAR[64] );
> CREATE INDEX MAL9_sin_index ON MAL9_single ( pos1 );
>
> From P
Hi,
I'm new to the list, but have been an enthusiastic sqlite user for years.
I've found the strangest issue today. I have a sqlite3 database that
contains the following table:
CREATE TABLE MAL9_single ( read_name VARCHAR[32], pos1 INTEGER, seq1
VARCHAR[64] );
CREATE INDEX MAL9_sin_index ON MAL9
3 matches
Mail list logo