ther of these OSes? Does anyone have
a sense as to how hard it might or might not be if it doesn't already
exist? Maybe it's not too hard if they're both POSIX compliant?
I know that Berkeley DB from sleepy cat has a vxworks port, but I would
really prefer to pursue sqlite.
Any
I have a database with 11 tables and a total of about 200k rows among
them. While I would not ordinarily put such a db in memory, I decided
to experiment with the :memory: version of the db. What I see is that
this db occupies about 39MB on disk, but as :memory: it pushes the
sqlite command-l
D. Richard Hipp wrote:
Jakub Adamek wrote:
> My experience is that SQLite makes roughly about 3x bigger files than MS
> Access. How would this change in 3.0?
>
SQLite is very storage efficient in the common case. In a typical
table, SQLite will use about 4 or 5 bytes of disk space for every 3
not reallocated.
Any clues as to 1) why so much memory is being used by these
transactions and/or 2) why is it not reused or released? Is there
anything we should be doing to prevent this?
This is version 2.8.15.
Any help greatly appreciated!
--Brett Granger
[EMAIL PROTECTED] wrote:
On Nov 4, 2004, at 3:42 PM, D. Richard Hipp wrote:
If we exit the process and then reopen the database in a new process,
all that memory is not reallocated.
Are you sure you have that right? What OS are you running?
Oops, tracked it down on our side... multi-threaded pro
5 matches
Mail list logo