From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Daniel Heath <daniel(at)heath(dot)cc> |
Cc: | Fabrízio Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Custom text type for title text |
Date: | 2019-01-04 13:30:37 |
Message-ID: | CAM-w4HNwJus72nWm-zTcOKb3eMUJ0-Dec03=0Akat3uJMdz14Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Policy on contrib has shifted over time. But generally we want to encourage
a lively ecosystem of extensions maintained outside of the Postgres source
tree so we avoid adding things to contrib when there's no particular
advantage.
The most common reason things are added to contrib is when the extension is
closely tied to internals and needs to be maintained along with changes to
internals. Modules like that are hard to maintain separately. But modules
that use documented general extensibility APIs should be able to be stable
across versions and live outside contrib.
On Thu 3 Jan 2019, 23:54 Daniel Heath <daniel(at)heath(dot)cc wrote:
> Would this also be appropriate for inclusion as contrib? I'm unfamiliar
> with the policy for what is / is not included there.
>
> Thanks,
> Daniel Heath
>
>
> On Fri, Jan 4, 2019, at 9:47 AM, Fabrízio de Royes Mello wrote:
>
>
>
> Em qui, 3 de jan de 2019 às 20:22, Daniel Heath <daniel(at)heath(dot)cc>
> escreveu:
>
> Hi All,
>
> I've frequently seen an issue in applications which store titles (eg of
> books, events, user profiles) where duplicate values are not properly
> vetted.
>
> The 'citext' type is helpful here, but I'd be keen to go further.
>
> I propose a 'titletext' type, which has the following properties when
> compared for equality:
> * Case insensitivity (like 'citext')
> * Only considers characters in [:alnum:] (that is, ignores spaces,
> punctuation, etc)
>
> This would be useful for a range of situations where it's important to
> avoid entering duplicate values.
>
> Given the discussion at
> https://www.postgresql.org/message-id/CAKFQuwY9u14TqG8Yzj%3DfAB0tydvvtK7ibgFEx3tegbPWsGjJpg%40mail.gmail.com
> <https://www.postgresql.org/message-id/CAKFQuwY9u14TqG8Yzj=fAB0tydvvtK7ibgFEx3tegbPWsGjJpg@mail.gmail.com> I'd
> lean towards making this type not automatically coerce to text (to avoid
> surprising behaviour when comparing text to titletext).
>
> Is a suitable patch likely to be accepted?
>
>
> You don’t need touch the core to do that. Just implement it as an
> extension and share throught some channel like pgxn.org.
>
> Note that citext also is an extension and released as a contrib module.
>
> Regards,
>
> --
> Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
> PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-01-04 13:33:05 | Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well |
Previous Message | Andrey Borodin | 2019-01-04 13:26:18 | Re: GiST VACUUM |