Oleg Broytmann escribió: > On Thu, Nov 08, 2007 at 06:03:37PM +0000, jonhattan wrote: > >> A workaround could be to set a length of 1000 if no length is specified >> and alternateId is present. >> 1000 for StringCol >> > > I'd rather raise an exception instead of silently imposing a limit where > the user clearly says "no limits". Silently "fixing" user errors is a bad > practice IMHO. > I agree, but a warning and setting the length to the max limit allowed by the backend will make code more portable.
>> 333 for UnicodeCol (1000 bytes / 3 bytes * char) >> > > Why 3 bytes?! > That's what I read in the bug report (utf8 = 3 bytes). Charsets and encoding is still a rough world for me. j > Oleg. > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
