On Feb 23, 2009, at 1:12 PM, johnf wrote:
> Some questions:
> Is it just non-ascii that is problem. Because I just read an
> article that
> implied that MsSQL does not support UTF-8 directly. But converts
> UTF-8 to
> UTF-16. But this is about the way the bytes are arranged.
>
> So is it the bytes or some other issues that we are dealing with?
It is how the bytes that are returned by the dbapi adapter are
interpreted. I just noticed that MySQLdb uses 'latin1' by default,
even if the database and table are set for utf-8. So I'm working on a
solution that will allow for more control over this encoding choice.
> And then there is the encoding stuff. Default for MsSQL is latin-1
> but what
> does that mean? And how does it relate to unicode, and UTF-8?
That's more information than can fit in an email. Try the following
links to see if they help clear up these issues:
http://farmdev.com/thoughts/23/what-i-thought-i-knew-about-unicode-in-python-amounted-to-nothing/
http://www.voidspace.org.uk/python/weblog/arch_d7_2006_02_04.shtml#e209
> Then there is the issue of python 3 (and I think 2.6) requiring
> unicode. How
> will this effect what we will do to fix the issue today?
It will make life much easier, as all text will be unicode, and we
won't have to constantly check to see if encoding/decoding is needed
when comparing values.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
