I thought this was fixed.... Maybe it was only fixed in mysql 4? Reactor should use the octet length.
Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Tuesday, August 08, 2006 2:35 AM To: [email protected] Subject: [Reactor for CF] maxlength and UTF8 (MySQL 5) I just noticed that with MySQL 5, Reactor uses CHARACTER_MAXIMUM_LENGTH for varchar columns which gives somewhat unexpected results for UTF8 data. e.g., varchar(32) -> maxlength 10; varchar(40) -> maxlength 13 The CHARACTER_OCTET_LENGTH column in the information_schema has the value I'd expect but I'm not familiar enough with MySQL to know whether I should simply be specifying column sizes that are bigger or whether Reactor should use the octet length instead? -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
