Dave,
> > [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 che
Hi,
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 upd
Hi,
ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
It's now working, but is excruciatingly slow. Is this also just covering
the problem, or will this be a usable solution when it finally finishes?
Just being curious: are you using
bayes_store_module Mail::SpamAssassin::BayesStore::MySQ
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
On 2011-06-23 18:40, Dave Wreski wrote:
Hi,
since so many have problems i share my mysql shemas :=)
`token` binary(5) NOT NULL,
Yes, the binary or varbinary is the key to a solution here.
Mucking with utf-8 vs latin-1 is just covering but not solving
the most glaring problem here, namely that
On 6/23/11 12:40 PM, Dave Wreski wrote:
It's now working, but is excruciatingly slow. Is this also just
covering the problem, or will this be a usable solution when it
finally finishes?
innodb optimizations, buffer sizes, index buffering, is all different
than myisam buffers.
look at the samp
Hi,
since so many have problems i share my mysql shemas :=)
`token` binary(5) NOT NULL,
Yes, the binary or varbinary is the key to a solution here.
Mucking with utf-8 vs latin-1 is just covering but not solving
the most glaring problem here, namely that a token must not be
associated with
On Wednesday June 22 2011 01:25:36 Benny Pedersen wrote:
> since so many have problems i share my mysql shemas :=)
>`token` binary(5) NOT NULL,
Yes, the binary or varbinary is the key to a solution here.
Mucking with utf-8 vs latin-1 is just covering but not solving
the most glaring problem he
On Tue, 21 Jun 2011 23:13:58 -0400, Dave Wreski wrote:
Use of uninitialized value $db_ver in concatenation (.) or string at
/usr/share/perl5/Mail/SpamAssassin/BayesStore/SQL.pm line 142.
using sql.pm not MySQL.pm, try the later one
Hi,
since so many have problems i share my mysql shemas :=)
please note that i expire som data not default done in current spamassassin
Your schema did not work for me. I deleted the existing database and
recreated it, then created the tables using your schema. When starting
to restore, a n
On Tue, 21 Jun 2011 21:03:25 -0230, Lawrence @ Rogers wrote:
What other option does he have? iconv??
if it can yes, but my mysql setup does not need iconv or my.cnf
changes,
On 21/06/2011 8:47 PM, Benny Pedersen wrote:
On Tue, 21 Jun 2011 22:16:05 +0300, Panagiotis Christias wrote:
After commenting out the utf8 definitions and reverting back to latin1
"sa-learn --restore" worked fine.
thanks for this report, but imho this should NOT be fixed in my.cnf
What oth
On Tue, 21 Jun 2011 17:18:30 -0400, Dave Wreski wrote:
I'll try the suggested my.cnf changes and restart the process.
since so many have problems i share my mysql shemas :=)
please note that i expire som data not default done in current
spamassassin
-- phpMyAdmin SQL Dump
-- version 3.4.1
On Tue, 21 Jun 2011 22:16:05 +0300, Panagiotis Christias wrote:
After commenting out the utf8 definitions and reverting back to
latin1
"sa-learn --restore" worked fine.
thanks for this report, but imho this should NOT be fixed in my.cnf
On 21/06/2011 7:01 PM, Dave Wreski wrote:
Hi,
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
On 21/06/2011 7:01 PM, Dave Wreski wrote:
Hi,
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
Hi,
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 useri
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 u
On Tue, Jun 21, 2011 at 5:47 PM, Mark Martinec wrote:
> Dave,
>
>> 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 w
Dave,
> 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 ar
On Tue, 21 Jun 2011 00:42:46 -0230
Lawrence @ Rogers wrote:
> On 20/06/2011 11:55 PM, Dave Wreski wrote:
> > Hi,
> >
> >>> I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm
> >>> trying to convert bayes to use mysql. The restore process fails
> >>> after a few minutes due to too many e
On 20/06/2011 11:55 PM, Dave Wreski wrote:
Hi,
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying
to convert bayes to use mysql. The restore process fails after a few
minutes due to too many errors:
dbg: bayes: error inserting token for line: t 1 0 1308114254 4fd2b3f2f0
dbg:
Hi,
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying
to convert bayes to use mysql. The restore process fails after a few
minutes due to too many errors:
dbg: bayes: error inserting token for line: t 1 0 1308114254 4fd2b3f2f0
dbg: bayes: _put_token: Updated an unexpected num
On 20/06/2011 10:09 PM, Dave Wreski wrote:
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying
to convert bayes to use mysql. The restore process fails after a few
minutes due to too many errors:
dbg: bayes: error inserting token for line: t 1 0 1308114254 4fd2b3f2f0
dbg: bayes
Hi,
This one is the current SQL schema and works
http://svn.apache.org/repos/asf/spamassassin/tags/spamassassin_current_release_3.3.x/sql/bayes_mysql.sql
- Lawrence
On 20/06/2011 7:34 PM, Dave Wreski wrote:
Hi,
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying
to convert
This one is the current SQL schema and works
http://svn.apache.org/repos/asf/spamassassin/tags/spamassassin_current_release_3.3.x/sql/bayes_mysql.sql
- Lawrence
On 20/06/2011 7:34 PM, Dave Wreski wrote:
Hi,
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying
to convert bayes
Hi,
I have an existing v3.3.2 on fedora14 (perl v5.12.3) that I'm trying to
convert bayes to use mysql. The restore process fails after a few
minutes due to too many errors:
dbg: bayes: error inserting token for line: t 1 0 1308114254 4fd2b3f2f0
dbg: bayes: _put_token: Updated an unexpected n
27 matches
Mail list logo
