21.09.2014 00:08, Richard Hipp kirjutas:
> On Sat, Sep 20, 2014 at 12:45 PM, Merike wrote:
>
>> 19.09.2014 04:21, Richard Hipp kirjutas:
>>> A simple script to reproduce the problem in the latest SQLite is as
>>> follows: CREATE TABLE t1(a INTEGER PRIMARY KEY, b INT
21.09.2014 15:12, RSmith kirjutas:
> Merike: Running Analyze did not fix the bug, it simply changed some
> internal-use values that allowed the bug to be circumvented. If you
> re-make a table as you had without running analyze, the problem will
> surely remain using the same codeba
't see a speedup after analyze. Should I try to minimize
it to a smaller database again where the bug still occurs, even after
analyze? Or will the change you made fix my original database speed as
well despite the analyze call not helping it?
Merike
_
lem has been fixed, you may
> stop reading now. If you are curious about the cause of the problem
> was, you may continue reading.
>
>
That's great to hear! Looking forward to next release :)
Merike
___
sqlite-users mailing list
sqlite
query has become slower
with newer versions?
Merike
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
5 matches
Mail list logo
