| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | y(dot)saburov(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Table 9.46. UUID Extraction Functions |
| Date: | 2026-10-09 05:35:31 |
| Message-ID: | 2565626.1791524131@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> On Thu, 2026-10-08 at 23:32 -0400, Tom Lane wrote:
>> I still wonder whether there's another solution path though.
>> We settled on &zwsp; because it fixed the major issue here,
>> but that doesn't mean there isn't a better answer.
> I think that an improved version could look as follows:
> uuid_extract_timestamp(
> '019535d9-3df7-79fb-b466-fa907fa17f9e'::uuid
> ) → 2025-02-23 21:46:24.503-05
Hmm, yeah, that could work so far as the PDF line-break problem
is concerned. Would it look too odd to HTML readers?
> Also, not everything (query results etc.) are likely to be copied and
> pasted by users. So I guess the way forward would be for me to spend
> some time with this. But then - is it *that* important?
Yup, that. If you want to press forward, have at it; I'm willing
to push fixes in this area.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg | 2026-10-09 12:46:36 | Documentation improvement patch |
| Previous Message | Laurenz Albe | 2026-10-09 05:29:43 | Re: Table 9.46. UUID Extraction Functions |