Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings. |
| Дата | |
| Msg-id | 1341607674.7092.3.camel@vanquo.pezone.net обсуждение |
| Ответ на | Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings. (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings
to Python encodings.
|
| Список | pgsql-hackers |
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.
В списке pgsql-hackers по дате отправления: