It turns out python uses UCS2 as the internal representation of unicode objects. This leaves us with with two options for codecs, 'internal' (with a potential for problems if you compiled python for UCS4) and 'utf16' (ucs2 and utf16 should be the same for our purposes). There can be some mixup if the server and the client are not of the same endianness, but without a test setup I can't say for sure. I guess a little testing my mssql people could clear this up and make a decision on the char codec.
On Dec 17, 7:28 am, mdipierro <[email protected]> wrote: > encode('ucs2') does not seem to work in python. > > traceback (most recent call last): > File "<stdin>", line 1, in <module> > LookupError: unknown encoding: UCS2 > > Any idea? > > On Dec 16, 4:15 pm, DenesL <[email protected]> wrote: > > > True achipa, MSSQL stores Unicode in the UCS-2 encoding scheme. > > > and to stir the > > pot:http://www.cmlenz.net/archives/2008/07/the-truth-about-unicode-in-python --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
