| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net>, 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: | 2021-03-25 09:44:49 |
| Message-ID: | 228b204a-f885-ce95-fdfd-4c0b41f5eed4@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10.03.21 14:52, David Steele wrote:
>> I thought about it a little bit more, and the prefix specification
>> has not too much sense (more if we implement this functionality as
>> function "unistr"). I removed the optional argument and renamed the
>> function to "unistr". The functionality is the same. Now it supports
>> Oracle convention, Java and Python (for Python UXXXXXXXX) and
>> \+XXXXXX. These formats was already supported.The compatibility witth
>> Oracle is nice.
>
> Peter, it looks like Pavel has aligned this function with unistr() as
> you suggested. Thoughts?
I haven't read through the patch in detail yet, but I support the
proposed details of the functionality.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2021-03-25 09:48:55 | Re: [PATCH] pg_permissions |
| Previous Message | Dilip Kumar | 2021-03-25 09:44:36 | Re: [HACKERS] Custom compression methods |