On Wed, Nov 29, 2023 at 10:26 AM Tom Lane wrote:
> I could see splitting this into three columns:
>
> 1. Preferred name (the standard's name, if it's a standard type)
>
> 2. Internal name (pg_type.typname), perhaps only if different from #1
>
> 3. Other aliases
>
I like the preferred name being
On 2023-Nov-29, Tom Lane wrote:
> Eric Hanson 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
Eric Hanson 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
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".
On Wed, Nov 29, 2023 at 8:10 AM Eric Hanson wrote:
> On Wed, Nov 29, 2023
On Wed, Nov 29, 2023 at 7:40 AM Peter Eisentraut
wrote:
> On 23.11.23 21:51, PG Doc comments form wrote:
> > I think there could be some clarification of what is a "name" vs.
> "alias" on
> > the datatypes table. Right now, what's in the "Aliases" column is
> sometimes
> > postgres's internal
On 23.11.23 21:51, PG Doc comments form wrote:
I think there could be some clarification of what is a "name" vs. "alias" on
the datatypes table. Right now, what's in the "Aliases" column is sometimes
postgres's internal type (e.g. `pg_catalog.int4`), and sometimes the "pretty
name", (e.g.
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/datatype.html
Description:
I think there could be some clarification of what is a "name" vs. "alias" on
the datatypes table. Right now, what's in the "Aliases" column is sometimes
