| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, vignesh C <vignesh21(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Vik Fearing <vik(at)postgresfriends(dot)org> |
| Subject: | Re: [PATCH] Add CANONICAL option to xmlserialize |
| Date: | 2026-03-30 11:27:25 |
| Message-ID: | 930c0f95-c82f-45f6-a74f-a13d2dc06679@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30/03/2026 11:44, Andrew Dunstan wrote:
> I note that your function returns xml, whereas Tom's suggestion was for
> a function returning text. I don't think there was any discussion on the
> point.
Indeed, there was no discussion regarding the return type.
My rationale for keeping it as xml was: the output is xml, callers can
immediately use the xml without casting, and nearly all other xml*
functions return xml. Is there a direct advantage of having this
function return text?
Thanks!
Best, Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-03-30 11:38:30 | Re: [PATCH] Add CANONICAL option to xmlserialize |
| Previous Message | Peter Eisentraut | 2026-03-30 11:27:12 | Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions |