> Bruno Delbono wrote: > > I've found that recovering bayes berkeley db databases can be a > > very big chore and would suggest that you move to a proper SQL > > datbase (MySQL, PostgreSQL, SQLite) as soon as possible. > > BerkeleyDB is horrible! Both in performance and reliability.
Michael Parker replied: > 1) This is bordering on FUD. Berkeley DB has it's uses, and as such > it is good to recognize those uses and use the right DB for the right > job. Indeed. For the record, in the time I've been using SA with Bayes (almost since it was introduced - I've been using SA since ~v2.2 or 2.3), I've *NEVER* had Bayes corruption, and I'm still using the "same" databases as I started with. I've had *other* problems related to how (auto)learning was implemented, and how expiry works, but that didn't corrupt the DB, just made the rest of the system bog down occasionally. <g> The closest thing to a BerkeleyDB-related issue that I've had was transferring a Bayes DB from a RH7.3 system to a Debian Woody system, where I had to do some magic to get the right version of the BDB library linked into Perl's DB_File module. (It didn't help that I'd added db4 to the RH system, when db3 was the "real" version of BDB shipping with the OS, and Debian shipped with (IIRC) db2 linked to DB_File.) -kgd -- Get your mouse off of there! You don't know where that email has been!
