Dave (and others), > dbg: bayes: error inserting token for line: t 1 0 1308114254 4fd2b3f2f0 > dbg: bayes: _put_token: Updated an unexpected number of rows.
I have opened three bug entries, the first one is directly in response to this problem report and brings a fix: [Bug 6624] BayesStore/MySQL.pm fails to update tokens due to MySQL server bug (wrong count of rows affected) https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6624 [Bug 6625] Bayes SQL schema treats bayes_token.token as char instead of binary, fails chset checks https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6625 [Bug 6626] Newer MySQL chokes on TYPE=MyISAM syntax https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6626 Dave, could you please revert my previous patch and apply instead the patch attached to Bug 6624 (applicable to 3.3, or just install trunk). Also consider the tiny fix to the schema as suggested by Benny Pedersen and found as an attachment to Bug 6625. This should avoid a problem if your SQL server defaults to UTF-8 or other character set with stricter checking than a plain Latin-1. Mark
