On 11/21/2013 11:41 PM, Fred Stluka wrote: > Clifford, > > I use: > - http://code.google.com/p/django-pyodbc/ > > No problem except that the MS SQL Server DB identifies itself > as using UTF-8, but actually contains Windows-1252 chars, so > we get UnicoeDecodeError a lot and have to repair the data.
Hi Fred, Is that because you had a legacy database with Windows-1252 characters in them? In other words, is this because of the data or because of django-pyodbc? -- Regards, Clifford Ilkay 647-778-8696 Dinamis <http://dinamis.com> -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/528FA684.3000202%40dinamis.com. For more options, visit https://groups.google.com/groups/opt_out.
