This page is about using in-memory SQLite databases.    
    
The file btree_rb.c attached to this page is a replacement binary-tree layer.    
It uses "red-black" binary trees. To use it, copy it over the btree.c file in    
the SQLite source tree and recompile. All tables created will be "in-memory".    
The filename supplied to sqlite_open is ignored.    
    
The following problems currently exist: {linebreak}  
* Virtually no testing done. All of the SQLite test suite that is practical to    
run with in-memory tables succeeds however. {linebreak}  
* No memory-leak testing has been done. {linebreak}  
* In some queries (ie. to process ORDER BY clauses and some sub-selects),    
SQLite uses binary-trees to hold intermediate data. The btree layer should not    
bother to store rollback information in these cases (but it currently does). 
{linebreak} 
* It's a compile time thing. It would be better if you could choose to create    
tables in-memory at run-time. {linebreak} 
 
The speedcompare.tcl script is a dodgy modification of DRH's speedcompare.tcl    
script. You run it using the "tclsqlite" interpreter.    
    
The speed.txt file contains performance stats comparing in-memory with on-disk    
tables.    
    
If anyone wants to develop this into a proper patch for SQLite and has any   
questions on how to do this, please post to the SQLite yahoo group.