From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, 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-12-01 23:05:21 |
Message-ID: | 2ae40e96-5799-a821-07b2-3dde0aa9a02d@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/30/20 8:14 AM, Peter Eisentraut wrote:
> 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.
>
>
>
Also, should this be an extension? I'm dubious about including such
marginal uses in the core code unless there's a really good case for it.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-12-01 23:07:17 | Re: Recent eelpout failures on 9.x branches |
Previous Message | Thomas Munro | 2020-12-01 22:50:21 | Re: Recent eelpout failures on 9.x branches |