Hi, I cannot comment on the speed of Berkeley DB, I am somewhat familiar with Oracles approach to licensing terms having spent somewhat more than £10M with them over the last five years :) You can accuse Ellison of many things (and I have. all of them unrepeatable) but being cheap isn't one of them, anyway I digress.
Point 1. Oracle can only change the licensing of Berkely DB from a certain point forward. Previous versions of licenses should still be perfectly applicable and useable. I am not a lawyer so check it out. This may work for you. Point 2. You don't say what your use case is for Berkeley or for SQLite. if you are after pure performance then it appears that Berkeley on the surface may be appropriate but do you actually need the speed? e.g. I have an application that uses SQLite3, I have no issue if the team make it 10x quicker, but to be honest for my needs, they could make it 100x slower and I would not notice a great deal of degradation in my application as I use SQLite for simple use, basically a cross platform simple filing system. 99.99% (and I've measured it) lies in the data processing rather than the database access and management. Point 3. As Howard has said look around and check out his stuff as well. It never hurts to have a different view on things and OpenLDAP LMDB may be a perfect fit for you. Just my 2p worth. Rob. On 14 Sep 2013, at 03:16, Howard Chu <h...@symas.com> wrote: > Patrick wrote: >> Hi Everyone >> >> After Oracle acquired Berkeley DB they changed the license. If people >> don't pay a significant licensing fee, it can now only be used for GPL code. >> >> I don't know Berkeley DB very well but I do know a moderate amount of >> Sqlite. >> >> I want to tinker with a compiler that uses DB, I was thinking about >> ripping it out and replacing it with Sqlite. Does this make sense? >> >> I know they are both zero configuration embedded DBs but DB is a >> key-value based one and I am assuming lighter, is this true? Any idea of >> how close they would be in terms of memory use and execution speed? > > BDB is much faster than SQLite, yes. In fact Oracle supplies a port of SQLite > that uses BDB as the underlying Btree engine instead of SQLite's native code, > and there's a significant performance gain. > > If you have an app that is comfortably using the key-value API of BDB it > would introduce major inefficiencies to convert it to using SQL. So no, this > doesn't seem like a logical action to take. > > If you're using BDB and want to switch off it because of the license issue, > try OpenLDAP LMDB instead. No license hassles, and also several times smaller > and faster than BDB. > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
