On Tue, Sep 28, 2010 at 2:01 AM, <sac.subscripti...@gmail.com> wrote:
> Hi, > Has anyone tried (successfully or unsuccessfully) anything along the line > of using just the B-tree APIs of sqlite as disk-based b+ tree library ? > Looking at the source code it looks like B-tree APIs are not really > exported > but could be, with little bit of a hacking. Please share your experiences. > Thanks in advance. > Several companies do the opposite - they strip out the B+tree layer from SQLite and replace it with their own storage engine. In other words, they use the SQL process facilities of SQLite to provide an SQL interface to their own B+tree layer. The storage layer in SQLite is very narrowly defined to do only those specific operations that the SQL engine needs. It is not a general-purpose B+tree library. It does not do everything you always wanted a B+tree library to do. I'm guessing you will be happier with a general-purpose library that is specifically designed to be accessible from applications. Furthermore, why would you want to use a low-level B+tree system when you have the full expressive power of SQL at your fingertips? Isn't that a little bit like chosing to program in assembly language when you have Python/Perl/Ruby/Tcl available? > > - sam > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
