Hi, > Curious: what are your reasons for using Bayes in SQL?
> > Are you sharing the DB among several machines? Or is this a single > > box/global bayes setup? > > > > > > Not yet, but that is the ultimate plan (to share the DB across multiple > servers). Also, I like the idea that the Bayes DB is backed-up > automatically along with all other databases on the server (we run a > cron script that performs the dump). Granted, it would be trivial to > schedule a call to "sa-learn --backup", but storing the data in SQL > seems more portable and makes it easier to query the data for reporting > purposes. > I have bayes in MySQL now, and I think it performs better than with just a flat file berkeley db. I believe it solved some locking/sharing issues I was having too. I converted to it a few months ago (relearned the corpus from scratch to mysql) with the intention of sharing between three systems, but the network latency and general performance between the systems for updates was horrible so they're all separate databases now. I'm still a mysql novice, so I don't doubt someone with more mysql networking experience could figure out how to share them between systems properly. I thought there would be one master system with two slaves, but instead they all seemed to be shared interactively for every query or update. For the InnoDB/MyISAM issue, if I'm understanding it correctly, I just edited the sql file I used to create the database, and I'm using InnoDB now without any issues on v3.3.2. I believe I used these instructions, with the sql modifications from above: http://www200.pair.com/mecham/spam/debian-spamassassin-sql.html Regards, Alex
