On Tue, 2007-11-27 at 18:01 +0100, Markus Gritsch wrote: > On 27/11/2007, David Turner <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-11-27 at 15:17 +0100, Markus Gritsch wrote: > > > > Conclusion: SQLObject is doing the wrong thing on many levels for MySQL. > > No it is not. Using UTF-8 is an ideal default. IMO the problem in > your example is that you do not use UTF-8 in MySQL. I use UTF-8 as > default encoding in MySQL and use there parameters in the SQLObject > connection string: > ?use_unicode=1&charset=utf8&sqlobject_encoding=utf-8 > > -> Everything works flawless. > > Markus > > P.S. Thank you for your example, I will look into it in more detail.
Do you mean that I need to configure MySQL itself in some way? If so, what setting do I need to change? If you mean that I need to change the table's column type, I just tried that (via mysql). Using the connection string above: select length(name), length(sname) from person; got: 3, 1 expected: 1, 3 So this is precisely backwards. ------------------------------------------------------------------------- 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
