From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-10 16:59:28 |
Message-ID: | CAM-w4HMJOiJgwpDQFWWphFoqqx-tbkg4uGNgkgbDstA_E-KBQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
On Tue., Mar. 5, 2019, 12:38 p.m. Pavel Stehule, <pavel(dot)stehule(at)gmail(dot)com>
wrote:
>
>
> út 5. 3. 2019 v 15:35 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>
>> David Steele <david(at)pgmasters(dot)net> writes:
>> > This thread has been very quiet for a month. I agree with Andres [1]
>> > that we should push this to PG13.
>>
>> I think the main thing it's blocked on is disagreement on what the
>> type name should be, which is kind of a silly thing to get blocked on,
>> but nonetheless it's important ...
>>
>
> I sent some others possible names, but probably this mail was forgotten
>
> What about "ctype" like shortcut for common type? carraytype,
> cnonarraytype?
>
> Regards
>
> Pavel
>
>>
>> regards, tom lane
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2019-06-10 17:33:38 | Re: doc: pg_trgm missing description for GUC "pg_trgm.strict_word_similarity_threshold" |
Previous Message | - - | 2019-06-10 16:47:42 | Re: Temp table handling after anti-wraparound shutdown (Was: BUG #15840) |