| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-10 07:22:07 |
| Message-ID: | fc07fb35381057bef38e4b83c868d87cf6e17ed2.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, 2026-10-09 at 20:25 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
>
> > For the UUID functions that the complaint was about, I simply added
> > regular spaces inside the parentheses, which in HTML looks like
> > uuid_extract_version( '41db1265-8bc1-4ab3-992f-885799a4af1d'::uuid ) → 4
> > I'd say that that is acceptable.
>
> Great idea, but when I looked at the rendered A4 PDF I saw why we'd
> put in the zwsps: without them, FOP decides that the best way
> to break these lines is like
>
> uuid_extract_version('41db1265-8bc1-4ab3-992f-885799a4af1d'::u-
> uid)
>
> which of course is really horrid (cf first attached screenshot).
> However, adapting your idea a bit, I tried putting spaces around
> the "::", and that renders far better (cd second attachment).
> So I'll run with that.
Thanks for taking care of that.
Strangely enough, I didn't see those horrid line breaks; for me,
the line broke at the arrow. It seems that there are some
variables unknown to me that influence the output.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kacper Kuras | 2026-10-10 12:41:13 | Re: E.6.3.2.1. Constraints |
| Previous Message | Bruce Momjian | 2026-10-10 02:23:49 | Re: 8.5.1. Date/Time Input |