Steven Woody wrote:
> On Sat, Jun 28, 2008 at 11:30 AM, dcharno <[EMAIL PROTECTED]> wrote:
>>> As an option, we also think about Berkeley DB, do you experts has
>>> experience using Berkeley DB on ARM/Linux with ulibc or glibc?
>> Berkeley DB may also be an option. It really depends upon what you are
>> trying to accomplish, what your data set looks like, etc.
>>
>> Ironically yes; I am translating Berkeley DB databases into SQLite for
>> analysis.
>
> :-) sounds like a good method
Except for legacy issues, I can't think of any reason you'd ever need both.
If your options are SQLite and Berkeley DB then a couple of points to
consider:
With SQLite, you obviously have the full power of SQL to model your
system's data and write arbitrarily complex queries to filter and
analyze your data. And SQL is standard so it is well documented and
easy for other team members to access.
Berkeley DB is a persistent hash table. Its good if your data is
primarily key/value based and you only need to do key lookup. But, its
really just a storage layer. It doesn't provide any type of query
capability for filtering or searching through your data -- all of that
has to be written as a layer above Berkeley DB by you.
Berkeley DB is a bit bigger than SQL
Compare the licenses. Be sure to read the license of Berkeley DB to
make sure it is compatible with your application.
http://en.wikipedia.org/wiki/Berkeley_DB#Licensing
SQLite is in the public domain, so you are free to do with it what you
please.
http://www.sqlite.org/copyright.html
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
