On 18 Jul 2014, at 4:45pm, Carlos Ferreira <car...@csiberkeley.com> wrote:
> This is on a standard windows 7 64 bits laptop. > > I am not using a shell command. I am using the win32/win64 precompiled Dlls. Can you please check to see if using VACUUM in the shell tool has the same problem with the same database ? This is because the SQLite team wrote the shell tool themselves and if there's anything wrong with it they have full source and can do lots of testing. Precompiled shell tool can be downloaded from the sqlite download page. If the shell tool handles VACUUM okay and your code doesn't, that indicates that the problem is in your code. That doesn't mean we won't help you figure out what's wrong, it just tells us where to look for anything unusual. > I will check the pragma integrity check... Please do. You can use the shell tool for that too, before you try VACUUM in it. > One thing I noticed before was that the maximum size for a blob inside a > record field is much smaller than what I imagined. > > If I use blobs with more than 200 Mb, things go wrong when trying to read it > back using the direct blob functions. > > I am going to check carefully if there is any other limit I am hitting Limits are here: <http://sqlite.org/limits.html> I don't think your problem is with limits, it's more likely to be memory handling in someone's code, but if the shell tool fails to do VACUUM we'll be very interested. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
