| From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 13 release notes, first draft |
| Date: | 2020-05-12 03:08:35 |
| Message-ID: | 5EBA1333.1080706@anastigmatix.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/11/20 22:48, Bruce Momjian wrote:
> On Mon, May 11, 2020 at 10:07:23PM -0400, Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> Allow Unicode escapes, e.g., E'\u####', U&'\####', to represent any
>>> character available in the database encoding, even when the database
>>> encoding is not UTF-8 (Tom Lane)
>>
>> How about "to be used for" instead of "to represent"? "Represent" kind
>> of sounds like we're using these on output, which we aren't.
>
> Uh, I think "used for" is worse though, since we are not using it. I
> don't get the "output" feel of the word at all.
'specify' ?
-Chap
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-05-12 03:15:46 | Re: PG 13 release notes, first draft |
| Previous Message | Amit Kapila | 2020-05-12 03:06:00 | Re: PG 13 release notes, first draft |