You are right... a unicode table does the job. I am wondering how it could work if my Oracle db doesn't support Unicode right now?
On Jun 14, 2:16 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Jun 14, 2007, at 12:15 PM, MattQc wrote: > > > > > I know it is not ideal, but I've solve the problem by changing the > > create_engine in pylons.database with: > > sqlalchemy.create_engine(uri, convert_unicode=True, **kwargs) > > Unicode() column type not working ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
