OpenEuphoria

RE: Berkeley DB with Euphoria

• Posted by Andy Serpa <renegade at earthling.net> Sep 27, 2002
• 411 views

Ray Smith wrote:
> Hi Andy,
> 
> I looked at wrapping Berkley DB awhile ago and come up against the
> same obstacles as you.
> 
> An alternative might be SQLite (strangely enough I happen to have a 
> wrapper for it already!!!! - see my web site below for euSQLite).
> SQLite implements a large subset of SQL and is a very fast embeddable
> SQL engine. Users of the SQLite mailing list claim databases many GB’s 
> In size without problems. 

I tried SQLite, and actually I converted your wrapper to use cdecl calls 
with fptr.e so I could translate it and have it still work.  Interesting 
that people have said they use it with many GB's (!) because that is why 
I gave up on it.  (My db will be around 1.2 GB and grow about 100mb a 
month).  I kept having problems creating a large database (and things 
got corrupted once in a while).  I even posting my problems to the 
mailing list (this is a few months back) but never got a response.  
Anyway, I liked SQLite and will probably use it for other things, but he 
is making new updates constantly (which is good), but I just didn't feel 
it was "rock-solid" and that's what I need.

> The other benefit of SQLIte over EDS and Berkley DB is the fact you get
> a SQL engine built in!
> 

I've been using MySQL for this project since then, but I've soured on 
the relational/SQL model (for this project).  It just isn't the most 
appropriate (SQLite was actually preferable with its typeless data) to 
what I'm doing.

Whereas Berkeley sounds perfect, and has got a rep of being very stable.

So I think having both Berkeley DB & SQLite easily available as 
third-party database solutions would be a "good thing."  As far as the 
obstables, there is only one -- I ain't got VC++ 6.0 and I ain't gonna 
buy it.  (I actually found binaries for version 4.0 something, but 4.1 
has a format change so I wanted to go with that.  Plus that's what I 
have the docs for.) There is no licensing problems or anything since it 
is open-source.  The binaries, once created, can be freely distributed.  
Just getting someone somewhere to build them shouldn't be impossible... 
(anybody?)


> So how big is to big for EDS?
> 

Well, 1.2 GB is too big.  It is not the size so much as the speed as EDS 
gets slower and slower as it grows...