It's known bug, will be fixed in 4.1.2
- Original Message -
From: "Juri Shimon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Noor Dawod" <[EMAIL PROTECTED]>
Sent: Wednesday, December 17, 2003 12:37 PM
Subject: Re: Invalid ENUM values after up
I have the same problem with cp1251 and, seems, it's a bug. I have posted
correspoding message two days ago. Without any reply 8(((
I migrate 3.23.55 -> 4.1.1 and I don't know about existing such problem in
4.0.
Look in your .frm - your field is in correct charset. More of,
inserts and updates of