Hi List, I was attempting to upgrade SQLObject from 0.7.1 to a newer version. I tried 0.9.x but there were a few problems with that with column names so I left it for now and went for 0.7.8.
I am accessing a MySQL database but unfortunately nested deep within the 0.7.8 code is a check for each character written to the database in a StringCol being in range(128). This is causing me a major headache because it was not picked up by my regression scripts (some of the fields in my existing database have characters > 128), and now I have users banging on my door wondering why my web app is failing all over the place. Not everywhere mind, just every time one of the fields is updated that has a >128 character in it. I know that it's probably not advisable to allow uses to store such data but it's there and useful. Shouldn't an API such as SQLObject not care about the integrity of the data is such a finicky way? A string is 0..255 byte and should allow me to write to it. It would not be uncommon to store byte data in a StringCol, surely? I am interested in why was this was done, because I cannot see it from my perspective. Is there a deeper rationale here? Secondly, I am progressing towards migrating to 0.9.x as fast as I can. Does the same check exist in 0.9.x? -- Alexander C. Le Dain, PhD Software Engineer ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
