Hi,
dbg: bayes: error inserting token for line: t 1 0 1308114254
4fd2b3f2f0 dbg: bayes: _put_token: Updated an unexpected number
of rows. [repeats ...]
Which version of MySQL?
Did you remember to replace TYPE=MyISAM with TYPE=InnoDB in the
schema (according to README.bayes) if you are using the recommended
Mail::SpamAssassin::BayesStore::MySQL as the bayes_store_module?
Please try the following patch (against 3.3.2), at least it should provide
more informative diagnostics:
[snip..]
I faced the same problem today. In my case, MySQL was configured to
use utf8 by default:
# my.cnf
[client]
default-character-set=utf8
[mysqld]
character-set-server=utf8
collation-server=utf8_unicode_ci
init_connect='set collation_connection = utf8_unicode_ci;'
After commenting out the utf8 definitions and reverting back to latin1
"sa-learn --restore" worked fine.
I'm using mysql version:
# mysql --version
mysql Ver 14.14 Distrib 5.1.56, for redhat-linux-gnu (x86_64) using
readline 5.1
Is there a difference between InnoDB and MyISAM in terms of training, or
can that change be made the initial training? Why is it so much slower
using InnoDB during training?
It looks like that may be my problem too. This is the result with your
patch:
dbg: bayes: database connection established
dbg: bayes: found bayes db version 3
dbg: bayes: Using userid: 2
dbg: bayes: database connection established
dbg: bayes: found bayes db version 3
dbg: bayes: using userid: 3
dbg: bayes: _put_token: Updated an unexpected number of rows: 3, id: 3,
token: 7�OR�
dbg: bayes: error inserting token for line: t 0 1 1308332646 37fc4f52eb
dbg: bayes: _put_token: Updated an unexpected number of rows: 3, id: 3,
token: ����Y
dbg: bayes: error inserting token for line: t 0 2 1308070890 d2eec4f659
I'll try the suggested my.cnf changes and restart the process.
Thanks,
Dave
