Igor,
You were indeed correct the SQL only version when the stack has say 8000 rows
was terrible. It took 20+ seconds in my application.
I re-wrote using a programatic approach, the resulting timing was astounding:
.1 second.
I suppose this is one of those odd cases where sql iteration
Yes that is much better.
Thanks again!
Ken
Igor Tandetnik <[EMAIL PROTECTED]> wrote: Ken wrote:
> The 22 is kind of like a time stamp.. (or you could just as easily
> add another column indicative of a timestamp.
>
> insert into stack values (1, 1234);
> insert into stack values (2, 1234);
Ken wrote:
I ran your cases and came up with this after adding the (22 record to
the stack)...
sqlite> explain query plan
...>
...> select s.id, p.id
...>from stack s, stackpop p
...> where s.value = p.value
...> and s.id < p.id
...> and (select count(*)
...>
Ken wrote:
The 22 is kind of like a time stamp.. (or you could just as easily
add another column indicative of a timestamp.
insert into stack values (1, 1234);
insert into stack values (2, 1234);
insert into stack values (6, 1234);
insert into stack values (9, 1234);
insert into stackpop value
4 matches
Mail list logo
