Re: [mbackup-devel] berkeley db3

[James O'K. <jo...@mi...>]

When I asked, I was already intent on using db3, I was mainly looking for 
some help/guidance on the most effective way to work with it. Almost all 
of my DB experience is in the sql world, so the lack of multiple fields in 
a table is a bit annoying.

That said, I'm about 90% finished with a bare-bones working index class 
using db3. I hope to commit the last of my changes to cvs in the next few 
days or so. Instead of merging everything into one data value and storing 
that in one key, I've opted to create several tables, each one with a 
different bit of data (date, hostname, location where stored, etc) and a 
table that maps filename to a unique number that can be used for the key 
of the other tables.

While, I don't think my implimentation is the best, it will work for now 
until someone else with more experience comes along and rewrites it. I 
mainly needed something that worked to test the index class API and to 
move forward with getting restores and such to work. My goal is to have a 
working restore in about 2 week depending on my work and class schedules.


An interesting side note, I took the cvs source code, and did a test
compile under cygwin in windows 2000, and aside from the lack of ftw(),
having to compile db3 and linking everything statically. This compiled and
worked.


-james