| From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Asif Naeem <asif(dot)naeem(at)enterprisedb(dot)com> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings. |
| Date: | 2012-07-06 21:12:44 |
| Message-ID: | 4FF754CC.3030401@wulczer.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 06/07/12 22:47, Peter Eisentraut wrote:
> 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.
So you're in favour of doing unicode -> bytes by encoding with UTF-8 and
then using the server's encoding functions?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Jbcooley | 2012-07-07 02:10:56 | npgsql - Npgsql2: Fix Include combined with Skip and/or Take using linq |
| Previous Message | Alvaro Herrera | 2012-07-06 20:58:39 | pgsql: Update libpq test expected output |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2012-07-06 21:24:12 | Re: WAL format changes |
| Previous Message | Peter Eisentraut | 2012-07-06 21:06:58 | Re: WAL format changes |