https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
Kent Oyer changed:
What|Removed |Added
CC||k...@mxguardian.net
--- Comment #9 from
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
Giovanni Bechis changed:
What|Removed |Added
CC||giova...@paclan.it
Resolu
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
--- Comment #7 from Sidney Markowitz ---
Also, I wondered if it is possible to get such an error by giving more than 5
bytes of binary string to a binary(5) column. When I looked at it I see that
bayes tokens are made from the lower 40 bits
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
--- Comment #6 from Sidney Markowitz ---
The first error is
dbg: bayes: tok_get_all: SQL error: Illegal mix of collations for operation
'in'
That can only be in MYSQL.pm line 464 which is the query constructed from
my $multi_sql = "SELEC
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
--- Comment #5 from Sidney Markowitz ---
I was too quick with my vote, Henrik's points are all good. I withdraw my +1,
not that I have to since a -1 overrides it until it is settled.
Looks like we could use a test case to reproduce this. Gi
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
--- Comment #4 from Henrik Krohns ---
Or if the problem is the actual perl $token variable being in UTF8 mode fed to
bind_param, is not the logical solution to utf8::encode it?
mysql_enable_utf8
"When set, a data retrieved from a textual c
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
Henrik Krohns changed:
What|Removed |Added
CC||apa...@hege.li
--- Comment #3 from
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
Sidney Markowitz changed:
What|Removed |Added
Severity|normal |blocker
CC|
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8042
Bill Cole changed:
What|Removed |Added
CC||billc...@apache.org
--- Comment #1 from
