From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: new polymorphic types - commontype and commontypearray |
Date: | 2019-06-14 04:09:36 |
Message-ID: | CAFj8pRCq+=tdb0PA8cHXG6bppVEqRrx7gjWeO4RtXkcPieoLaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
čt 13. 6. 2019 v 2:37 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Greg Stark <stark(at)mit(dot)edu> writes:
> > The proposals I see above are "commontype", "supertype", "anycommontype",
> > and various abbreviations of those. I would humbly add "compatibletype".
> > Fwiw I kind of like commontype.
> > Alternately an argument could be made that length and typing convenience
> > isn't really a factor here since database users never have to type these
> > types. The only place they get written is when defining polymorphic
> > functions which is a pretty uncommon operation.
> > In which case a very explicit "anycompatibletype" may be better.
>
> I could go with "anycompatibletype". That would lead us to needing
> related names like "anycompatiblearraytype", which is getting annoyingly
> long, but you might be right that people wouldn't have to type it that
> often.
>
> Also, given the precedent of "anyarray" and "anyrange", it might be
> okay to make these just "anycompatible" and "anycompatiblearray".
>
I like anycompatible and anycompatiblearray.
I'll update the patch
Regards
Pavel
> [ wanders away wondering if psql can tab-complete type names in
> function definitions ... ]
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Lakhin | 2019-06-14 04:16:15 | Re: Fix inconsistencies for v12 (pass 2) |
Previous Message | David Rowley | 2019-06-14 03:57:45 | Re: PostgreSQL 12: Feature Highlights |