From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Eric Hanson <eric(at)aquameta(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: "name" vs "alias" in datatype table |
Date: | 2023-11-29 16:42:54 |
Message-ID: | 202311291642.xumbxwgwquip@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2023-Nov-29, Tom Lane wrote:
> Eric Hanson <eric(at)aquameta(dot)com> writes:
> > The larger point being, the "name" vs "alias" paradigm presented in this
> > table does not accurately represent PostgreSQL, and conveys an inaccurate
> > picture of the relationship between type names. int4 is not an "alias".
>
> I agree that this could be improved, mainly because it's far from
> clear what the internal name of each type is (and there's at least
> one case where the internal name is not shown at all).
Maybe we could split this into multiple *tables*. The main one would be
what we already have except the aliases column is removed, and serial
types removed; the second table would list serial pseudo-types, without
aliases; the third one would have unofficial names (internal names and
other aliases) for types listed in the other two.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"The ability of users to misuse tools is, of course, legendary" (David Steele)
https://postgr.es/m/11b38a96-6ded-4668-b772-40f992132797@pgmasters.net
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Hanson | 2023-11-29 18:27:08 | Re: "name" vs "alias" in datatype table |
Previous Message | Tom Lane | 2023-11-29 16:26:46 | Re: "name" vs "alias" in datatype table |