On 2014/05/14 09:56, Kleiner Werner wrote:
Hello,
A collegue has strange behavior with a sqlite database.
A "colleague" hey? This is not a "Dear John" column, you can be honest. :)
The original DB is about 13 MB.
After storing 40 entries in a table the disk space is double and about 26 MB.
It is a program written in C# and used the SQLite datareader.
Now, suddenly he cannot get any returns from an simle select.
If he executes the same SELECT in the Firefox Plugin SQLite Administrator it
works fine.
It is a simple select of a table with some integer columns.
40 Entries of what? 40 quarter-MB Blobs would would more than suffice to cause that expansion. Other size-inducing culprits can be
triggers adding a lot of stuff upon inserts, or foreign keys, etc.
Getting returns from a select should work always if the integrity check passes, unless the select statement is wrong. You might try
to check that select in another SQLite tool because the Firefox one might automatically correct some silly error before passing it
on to the SQLite engine, which your Datareader doesn't. Either way, if the SELECT works in other things, but not in your's, then the
error must be in your code. Try to check it against other things, and if still wrong, paste the C code here - some of these people
on the list do use those same mechanisms and might spot an easy fix and/or optimization for you.
Try to post only the relevant code, none of us like reading Phone-book-sized
code blocks, but will try to check for the obvious.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
