Re: Selecting strict, immutable text for a composite type.

From: Steven Lembark <lembark(at)wrkhors(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org, lembark(at)wrkhors(dot)com
Subject: Re: Selecting strict, immutable text for a composite type.
Date: 2018-05-11 04:49:24
Message-ID: 20180510234924.01bf3685@wrkhors.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 10 May 2018 17:38:48 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Yeah, but that's not what you did.
>
> I think you could make that work with
>
> exclude using gist (
> lat_lng_text(location) with =,
> effective with &&
> )
>
> but it's not going to apply the function without you telling it to.

Q: Why does it work with enums?

e.g., If I create a type foo_t as enum (...) and install the function
foo_text on foo_t the gist works. Why would the presence of a text
verison of the composite not get used the same way?

If the function works I'm happy, I just don't see the reasoning
behind having the enum's supported automatically and the composite
not handled.

enjoi

--
Steven Lembark 1505 National Ave
Workhorse Computing Rockford, IL 61103
lembark(at)wrkhors(dot)com +1 888 359 3508

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2018-05-11 04:57:16 Re: Selecting strict, immutable text for a composite type.
Previous Message Adrian Klaver 2018-05-10 22:43:39 Re: Domain based on TIMEZONE WITH TIME ZONE