| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marthin Laubscher <postgres(at)lobeshare(dot)co(dot)za> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Custom type's modifiers |
| Date: | 2024-06-27 17:05:25 |
| Message-ID: | 1754334.1719507925@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marthin Laubscher <postgres(at)lobeshare(dot)co(dot)za> writes:
> I confess to some uncertainty whether the PostgreSQL specific x::y notation and the standards based CAST(x AS y) would both be addressed by creating a cast.
Those notations are precisely equivalent, modulo concerns about
operator precedence (ie, if x isn't a single token you might have
to parenthesize x to get (x)::y to mean the same as CAST(x AS y)).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-06-27 18:35:53 | Re: Visibility bug with prepared transaction with subtransactions on standby |
| Previous Message | Marthin Laubscher | 2024-06-27 17:01:10 | Re: Custom type's modifiers |