From: | Lukas Eder <lukas(dot)eder(at)gmail(dot)com> |
---|---|
To: | peter(dot)eisentraut(at)2ndquadrant(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15356: Inconsistent documentation about CREATE TYPE |
Date: | 2018-11-13 10:01:45 |
Message-ID: | CAB4ELO4U9j==U+knbtagTUO5O2w=NaE_cOmmk63DeOgL3R+HEQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Nov 13, 2018 at 10:45 AM Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 28/08/2018 14:56, PG Bug reporting form wrote:
> > The CREATE TYPE documentation [1] specifies that enum types without any
> enum
> > labels are possible:
> >
> > CREATE TYPE name AS ENUM ( [ 'label' [, ... ] ] )
> >
> > I can confirm this. The following statement works well:
> >
> > CREATE TYPE e AS ENUM ();
> >
> > However, further down in the same documentation page, we can see:
> >
> > "Enum types take a list of one or more quoted labels"
> >
> > It should read "zero or more quoted labels". I suspect this should be
> > adapted on all documentation pages from PostgreSQL 9.0 onwards. In 8.4,
> the
> > documentation was consistent [2]
>
> Right. How about the attached patch?
>
Makes sense, thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Jürgen Strobel | 2018-11-13 12:44:03 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
Previous Message | Moritz Bauer | 2018-11-13 09:58:18 | pgAdmin 4 3.5 fails to start properly in Windows 7 |