Re: BUG #14232: Possible mistake in the documentation

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "aouda(dot)h(at)me(dot)com" <aouda(dot)h(at)me(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14232: Possible mistake in the documentation
Date: 2016-07-07 00:58:53
Message-ID: CAKFQuwZC5SkCobik2f9ANoRx5bM-3qdkn2fpVXVoyq2MUfGpvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wednesday, July 6, 2016, <aouda(dot)h(at)me(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14232
> Logged by: Hicham Aouda
> Email address: aouda(dot)h(at)me(dot)com <javascript:;>
> PostgreSQL version: 9.5.3
> Operating system: All
> Description:
>
> On page 1151 43.3.4. Composite Types
> of the pdf documentation for 9.5.3
> I suspect a mistake:
>
> it should be :
>
> CREATE TYPE employee AS (
> name text,
> salary integer,
> age integer );
>
> and not
>
> CREATE TABLE employee (
> name text,
> salary integer,
> age integer );
>
>
>
It's functionally correct. Every table you create automatically has a type
of the same name and structure.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Hicham AOUDA 2016-07-07 01:00:00 Re: BUG #14232: Possible mistake in the documentation
Previous Message Peter Geoghegan 2016-07-07 00:48:06 Re: BUG #14150: Attempted to delete invisible tuple