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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Steven Lembark <lembark(at)wrkhors(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Selecting strict, immutable text for a composite type.
Date: 2018-05-11 04:57:16
Message-ID: CAKFQuway0Ou49jvzNv_Wpe_zT-yNp5Tuu6JucKsSGb5UKeXBYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday, May 10, 2018, Steven Lembark <lembark(at)wrkhors(dot)com> wrote:
>
> Q: Why does it work with enums?

Guessing because enums are not composites; they are scalar and most scalar
types in core seem to be covered by the extension.

> e.g., If I create a type foo_t as enum (...) and install the function
> foo_text on foo_t the gist works.
>

You should ifnd it works even without the existence of the foo_text
function.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ben Hood 2018-05-11 07:01:45 Re: Domain based on TIMEZONE WITH TIME ZONE
Previous Message Steven Lembark 2018-05-11 04:49:24 Re: Selecting strict, immutable text for a composite type.