Yup, I reported the exact same problem here on this list only a few weeks back. I was using MySQL 5.0.22. Upgrading to 5.0.24 fixed it.
On 9/7/06, Angus Johnson <[EMAIL PROTECTED]> wrote:
Hi Nando, This is probably a MySQL bug. What version are you running? Prior to 5.0.24 there were issues with incorrect metadata stored in informationschema.columns. Reactor's data.mysql.ObjectDAO.readFields() uses character_maximum_length for length. Take a look in the informationschema.columns for the column throwing the error and see if the values for character_maximum_length and character_octet_length are correct. Octet_length is storage bytes. Examples below: character_maximum_length:character_octet_length varchar(10) 10:30 varchar(64) 64:192 From memory I was using 5.0.16 which had these values swapped around and I had to edit the SQL in readFields() to fix. Since upgraded to 5.0.24 and no probs. Hope that helps. Angus On 08/09/06, Nando <[EMAIL PROTECTED]> wrote: > > I'm using the latest revision of Reactor, 346, and MySQL5 in Unity and running into a problem. What's happening is that with any varchar field, the generated files are dividing the length of the field by 3 and placing a maxlength value 1/3 of what it's supposed to be in the generated cfqueryparam tags. So for instance, i have a varchar 35 for a UUID named subscriberId, and the query params in the generated files come out like this: > > <cfqueryparam cfsqltype="cf_sql_varchar" > > maxlength="11" > > value="#arguments.to.subscriberId#" > /> > > Then the insert or update throws an error. This looks like a bug of some sort to me, unless someone can tell me what i might be doing wrong? I'll submit it as such unless someone says something to the contrary. > > thanks, > Nando
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
