Re: proposal: unescape_text function
| От | Andrew Dunstan |
|---|---|
| Тема | Re: proposal: unescape_text function |
| Дата | |
| Msg-id | 2ae40e96-5799-a821-07b2-3dde0aa9a02d@dunslane.net обсуждение исходный текст |
| Ответ на | Re: proposal: unescape_text function (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
| Ответы |
Re: proposal: unescape_text function
|
| Список | 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
В списке pgsql-hackers по дате отправления: