bayes in MySQL with replication

[Rick Cooper]

 > -----Original Message-----
 > From: mailscanner-bounces at lists.mailscanner.info 
 > [mailto:mailscanner-bounces at lists.mailscanner.info] On 
 > Behalf Of Julian Field
 > Sent: Friday, February 22, 2008 11:50 AM
 > To: MailScanner discussion
 > Subject: Re: bayes in MySQL with replication
 > 
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > 
 > 
 > Jason Ede wrote:
 > >
 > > Many thanks for that... just what I was looking for...
 > >
 > > I also saw a
 > >
 > > 080222 15:38:55 [ERROR] Slave: Error 'You have an error in 
 > your SQL 
 > > syntax; check the manual that corresponds to your MySQL 
 > server version 
 > > for the right syntax to use near 'ON DUPLICATE KEY UPDATE 
 > spam_count = 
 > > GREATEST(spam_count + '0', 0),
 > >
 > > ' at line 2' on query. Default database: 'sa_bayes'. 
 > Query: 'INSERT 
 > > INTO bayes_token
 > >
 > > (id ON DUPLICATE KEY UPDATE spam_count = 
 > GREATEST(spam_count + '0', 0),
 > >
 > > ham_count = GREATEST(ham_count + '1', 0),
 > >
 > > atime = GREATEST(atime, '1203694258')Ã', Error_code: 1064
 > >
 > That capital A with an accent of some sort right at the end 
 > of the query 
 > it reports looks very suspicious to me...

That really didn't look suspicous to me, I don't know his OS but I can tell
you that character will appear all over the place in say,
CENTOS if you leave the LANG setting at the default. I never bothered trying
to see exactly what white space character is being
Interpreted but you will see it when you, say cat or grep a log or, most
annoying, if you look at any man page. Setting LANG=en_US.iso88591 makes
them all go away nicely. So I assumed that was the issue here.

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.