does it (ok, boring. it has to be this way.). If needed
everything can be replaced.
Case closed until more evidence found.
--
Holger Lembke
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite
lem until complains come in and get nasty
I tend to d.)
--
Holger Lembke
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
from 3 MB to 85 MB.
--
Holger LembkeChallenge the net: 3d Traceroute http://d3tr.com/
+49-531-334676 56 Tage auf See: http://56tage.de/
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
all would end.
But main concern was that I did something wrong and had an error in my code.
Case closed for me. Thanks!
--
Holger Lembke
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
KB) and end at 6.740 KB after the 100 more
FILLs and an optimize after each FILL.
Thats very OK for me. :-)
Thanks for the long answer, I think the WIKI page
http://www.sqlite.org/cvstrac/wiki?p=FullTextIndex should contain the
"optimize" trick.
--
Holger Lembke
multiple times I get a growing database. select
count(*) from ft and ft_content stays at 400, ft_segdir stays at 30.
But select count(*) from ft_segments is raising, from 756, 1237 to 2100 and
so on. Ok, that explains the growing of my database file.
Wh
6 matches
Mail list logo