Re: Table 9.46. UUID Extraction Functions

Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> I felt inspired enough to take a look, and I found only three places
> that looked like likely things that someone might copy and paste.

Ah, excellent point. If we consider only fragments of SQL then yes,
the problem gets way smaller.

> The first didn't actually need a line break in either the US letter
> or A4 format, so I simply removed the &zwsp;. I wonder if some other
> documentation format might need it though...

Dunno, I'm not seeing a warning there either. Perhaps that zwsp
dates from before one of the mass reformattings we've done over
the years? I didn't bother doing any archaeology though.

> 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.

regards, tom lane