Peter Eisentraut <pete...@gmx.net> writes: > On Wed, 2009-09-23 at 10:20 -0400, Tom Lane wrote: >> comet_moth, gothic_moth: these are failing the new plpython_unicode >> test >> in locale cs_CZ.ISO8859-2. Somebody needs to do something about that. >> If it's left to me I'll probably just remove the test that has >> multiple >> results.
> This is, at first glance, not a valid variant result. It's a genuine > failure that needs investigation. I can't reproduce the problem with > the equivalent locale on Linux, so Zdenek might need to look into it. Uh, I can reproduce it just fine on Fedora 11, and OS X too. These are running python 2.6 and 2.6.1 respectively ... maybe the behavior is python version dependent? As far as I can tell, PLyObject_ToDatum is invoking PLyUnicode_Str and then PyString_AsString, and what it gets back from the latter is (in C string notation) "\200\0". Possibly what this means is that python thinks that that is the correct LATIN2 representation of \u0080. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers