On fre, 2012-07-06 at 18:53 +0300, Heikki Linnakangas wrote: > > What shall we do about those? Ignore them? Document that if you're sing > > one of these encodings then PL/Python with Python 2 will be crippled and > > with Python 3 just won't work? > > We could convert to UTF-8, and use the PostgreSQL functions to convert > from UTF-8 to the server encoding. Double conversion might be slow, but > I think it would be better than failing.
Actually, we already do the other direction that way (PLyUnicode_FromStringAndSize) , so maybe it would be more consistent to always use this. I would hesitate to use this as a kind of fallback, because then we would sometimes be using PostgreSQL's recoding tables and sometimes Python's recoding tables, which could became confusing. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
