Hmm... do you think mixing StringCol and UnicodeCol could cause this? I never thought about it but maybe I need to upgrade all the columns to be Unicode instead of having mixed Unicode/String Cols. I'll see what that does later today.
-Ian On 10/31/06, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > I didn't follow the beginning of this thread, but a quick note that > you should be able to use unicode when you use UnicodeCol objects. > The UTF-8 encoding/decoding is handled in Python then. > > Kevin > > On Oct 31, 2006, at 4:58 PM, Ian Wilson wrote: > > > > > Yeah I was kind of looking to stay with mysql because I use it > > everywhere else and I am more familiar with it than PostGre and > > sqllite. There has to be something I can do to fix it. > > > > > > On 10/31/06, Ed Singleton <[EMAIL PROTECTED]> wrote: > >> > >> I had the same thing and fixed it by using sqlite instead of MySQL. > >> PostGre doesn't seem to have the problem either. > >> > >> Ed > >> > >> On 31/10/06, Ian Wilson <[EMAIL PROTECTED]> wrote: > >>> > >>> Thanks but I changed sqlobject_encoding=utf-8 to > >>> sqlobject_encoding=utf8 and I still get the same error. What else > >>> could I try? > >>> > >>> -Ian > >>> > >>> On 10/31/06, Max Ischenko <[EMAIL PROTECTED]> wrote: > >>>> > >>>> > >>>> Try to append sqlobject_encoding=utf8 to your sqlobject.dburi in > >>>> dev.cfg. > >>>> > >>>> Max. > >>>> > >>>> > >>>>> > >>>> > >>> > >>>> > >>> > >> > >>> > >> > > > > > > > > -- > Kevin Dangoor > TurboGears / Zesty News > > email: [EMAIL PROTECTED] > company: http://www.BlazingThings.com > blog: http://www.BlueSkyOnMars.com > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
