| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Asif Rehman <asifr(dot)rehman(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: unescape_text function |
| Date: | 2020-11-30 13:14:30 |
| Message-ID: | 85e92b87-c02e-e2fd-1ddc-e2f82b3d2b57@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-11-29 18:36, Pavel Stehule wrote:
>
> I don't really get the point of this function. There is AFAICT no
> function to produce this escaped format, and it's not a recognized
> interchange format. So under what circumstances would one need to
> use this?
>
>
> Some corporate data can be in CSV format with escaped unicode
> characters. Without this function it is not possible to decode these
> files without external application.
I would like some supporting documentation on this. So far we only have
one stackoverflow question, and then this implementation, and they are
not even the same format. My worry is that if there is not precise
specification, then people are going to want to add things in the
future, and there will be no way to analyze such requests in a
principled way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2020-11-30 13:16:28 | Re: Improving spin-lock implementation on ARM. |
| Previous Message | Michael Paquier | 2020-11-30 13:13:02 | Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2 |