Hi, Jack,
Regarding: "I use sqlite3 on resource limited embedded devices, and
it provide only 250K memory for sqlite. Now, I have a table named
test_tab,whose size is 300K bytes."
Do you mean 250K bytes of persistent memory (flash file system) for the
database, or do you mean 250K bytes of RAM memory for sqlite and it's
cache to run in?
I'm not sure I'm qualified to answer, but you might look at:
-- compressing your data before storing in the database, though
you'd need at least some cleartext if you need indices.
-- removing any indicies you can do without (or shorten the length
of an essential one).
-- More drastic measures such as using a PRAGMA to disable the
rollback journal.
*If* 250Kbytes is all you have for persistent storage, you might need to
consider whether
-- Sqlite, even though very "light," may be more than your
application can tolerate.
-- You'll need heavy compression to make this work with even simple
data storage; maybe the memory on the device is simply undersized for
the requirements.
Regards,
Donald
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
