Re: implement CAST(expr AS type FORMAT 'template')

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Haibo Yan <tristan(dot)yim(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: implement CAST(expr AS type FORMAT 'template')
Date: 2026-07-09 07:20:29
Message-ID: 488d3554-0564-443e-b08a-66e0da66f736@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.07.26 19:14, Haibo Yan wrote:
> The cases where I think a generic mechanism could be useful are
> broader than that. For example:
>
> text <-> date/time using datetime templates
> text <-> numeric using number templates
> text <-> bytea using hex/base64/escape
> text/bytea <-> extension types
> using external representations such as
> WKT/WKB/GeoJSON for geometry types
One problem I see is that this would dictate that there is only one
possible format language for each of these conversions.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-07-09 07:41:57 Re: Truncate logs by max_log_size
Previous Message Peter Eisentraut 2026-07-09 07:18:16 Re: implement CAST(expr AS type FORMAT 'template')