Hi
Here are the results of my speed testing:
Recompile: 85.937500 total, 0.017188 avg.
Temporary table: 87.00 total, 0.017400 avg.
Virtual table: 85.562500 total, 0.017112 avg.
As you can see the whole thing was really a pointless exercise :( I
had imagined the impact of 'prepare' to be much
hy it may not be practical, but it would be a
nice feature. Is this even part of the SQL standard?
-Clark
- Original Message
From: Sam Thursfield <sss...@gmail.com>
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Sent: Wednesday, January 14, 2009 1:26:14 PM
Subject
On Wed, Jan 14, 2009 at 4:38 PM, Igor Tandetnik wrote:
> Sam Thursfield wrote:
- binding text results in SELECT * ... WHERE foreign.id IN ("4. 3,
6, 7") ...; which of course doesn't work.
>>
>> Do you know off hand whether this method would be
MikeW writes:
>
> If your list values are relatively small you could use a set
> of bits for your IN clause and use
> bitwise: WHERE ((1< encodes the required elements as bits set to 1.
>
..snip..
>
> Regards,
> MikeW
Oops, that
Sam Thursfield writes:
>
> Hello everyone,
> I have a question which I'm hoping someone who knows a bit about
> SQlite's internals can answer easily.
>
> I have a query such as this:
>
> SELECT * FROM local INNER JOIN foreign ON local.foreign_id =
> foreign.id WHERE foreign.id IN
Sam Thursfield wrote:
>>> - binding text results in SELECT * ... WHERE foreign.id IN ("4. 3,
>>> 6, 7") ...; which of course doesn't work.
>
> Do you know off hand whether this method would be much faster than
> compiling a new query for each new list of ids?
I'm not sure I
Hi Igor,
Thanks for your reply.
On Wed, Jan 14, 2009 at 4:16 PM, Igor Tandetnik wrote:
> Sam Thursfield wrote:
>> I have a query such as this:
>>
>> SELECT * FROM local INNER JOIN foreign ON local.foreign_id =
>> foreign.id WHERE foreign.id IN (4, 3, 6, 7)
Sam Thursfield wrote:
> I have a query such as this:
>
> SELECT * FROM local INNER JOIN foreign ON local.foreign_id =
> foreign.id WHERE foreign.id IN (4, 3, 6, 7) ORDER BY local.name;
>
> Here the list of numbers in the WHERE clause is subject to change. How
> possible do you
Hello everyone,
I have a question which I'm hoping someone who knows a bit about
SQlite's internals can answer easily.
I have a query such as this:
SELECT * FROM local INNER JOIN foreign ON local.foreign_id =
foreign.id WHERE foreign.id IN (4, 3, 6, 7) ORDER BY local.name;
Here the list of
9 matches
Mail list logo