Re: Table 9.46. UUID Extraction Functions - Mailing list pgsql-docs

From Laurenz Albe
Subject Re: Table 9.46. UUID Extraction Functions
Date
Msg-id fc07fb35381057bef38e4b83c868d87cf6e17ed2.camel@cybertec.at
Whole thread
In response to Re: Table 9.46. UUID Extraction Functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Table 9.46. UUID Extraction Functions
List pgsql-docs
On Fri, 2026-10-09 at 20:25 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz.albe@cybertec.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



pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 8.5.1. Date/Time Input
Next
From: Kacper Kuras
Date:
Subject: Re: E.6.3.2.1. Constraints