Re: [sqlite] New to SQLite, couple of questions
"Andrew Piskorski" <[EMAIL PROTECTED]> wrote: On Mon, Dec 27, 2004 at 08:51:11PM -0800, Roger Binns wrote: Why do you need SQLite if you want everything in memory? All you gain is an SQL Parser to operate on the data structures instead of just doing it directly yourself. All? You gain the relational model, which in some cases could be a huge win. I have considered using in-memory SQLite (haven't actually done it yet) rather than lots of ugly hash tables for exactly that reason. That would be true for smaller amounts of data. The OP was concerned about the 2GB address space limit. Bypassing SQLite in that case means your code can know very specifically what all data types are, can have perfect hash functions and can make memory vs cpu tradeoffs as appropriate. It can also do interning if there are frequent common values. And it can do things like allocate all the memory at program startup rather than throughout execution in order to be resilient to when the address space does fill up. Other than some circumstances such as transient data, the in memory database doesn't buy you much. You can always tell SQLite how much memory to use to get desired performance, and having a disk based database makes it easy to have checkpointing. Roger
Re: [sqlite] New to SQLite, couple of questions
On Mon, Dec 27, 2004 at 08:51:11PM -0800, Roger Binns wrote: > Why do you need SQLite if you want everything in memory? All you gain is > an SQL Parser to operate on the data structures instead of just doing it > directly yourself. All? You gain the relational model, which in some cases could be a huge win. I have considered using in-memory SQLite (haven't actually done it yet) rather than lots of ugly hash tables for exactly that reason. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/
Re: [sqlite] New to SQLite, couple of questions
What are some of the limitations of using memory tables (operations, counts, etc)? Looking at Linux 32bit intel implementation (RH) and want to do some larger tables all in memory. How large you ask ... as large as I can fit in the typical 2gig workspace. Why do you need SQLite if you want everything in memory? All you gain is an SQL Parser to operate on the data structures instead of just doing it directly yourself. On the other hand if you use on disk databases you can tell SQLite how much memory to use as a page cache. The default is 2MB. Roger
[sqlite] New to SQLite, couple of questions
What are some of the limitations of using memory tables (operations, counts, etc)? Looking at Linux 32bit intel implementation (RH) and want to do some larger tables all in memory. How large you ask ... as large as I can fit in the typical 2gig workspace. Also does/can SQLite support 64 Bit O/S native so I could easily get past the some of the memory limits. I just started looking at SQLite and it looks awsome, as well as for other projects kicking around I found some native Delph/C++Builder components as well. Thanks for the newbie help :-) Sandy
