http://bugzilla.spamassassin.org/show_bug.cgi?id=3091
------- Additional Comments From [EMAIL PROTECTED] 2004-02-25 16:10 ------- Here is the blurb I'm adding to README.bayes for the fix of this bug: The Bayes SQL store code should work out of the box with any database server that provides/supports the GREATEST() function. The databases that natively support this are MySQL and Oracle (if you know of others please let us know). Addition of a user defined function with PostgreSQL is trivial, in fact the bayes_pg.sql code includes a GREATEST() function that can be used. Any other database that allows you to define your own GREATEST() function should work just fine, you can find several implementations for DB2 via Google. Unfortunately, this causes support for some databases to no longer be supported, for instance SQLite. In general, I think this is ok simply because performance wise you want to be using a true database server for this feature. If this change causes your favorite database server to no longer be supported feel free to speak up, we can work with you to make things work. I guess what I'd ask other devs, is this acceptable? In my opinion we aren't locking anyone out of using the SQL feature. No one in their right mind would attempt to run this on an under powered database server. We are adding one small speed bump for Postgres and DB2 users, but from my reading should be a very small bump. There is one other way I could go to fix the bug but it's a) not optimal performance wise, b) ugly and c) I really don't want to do it. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
