Re: Typed table DDL loose ends

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Noah Misch <noah@leadboat.com>, pgsql-hackers@postgresql.org, Peter Eisentraut <peter_e@gmx.net>
Date: 2011-04-18T15:46:50Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Prevent a rowtype from being included in itself.

Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Apr 18, 2011 at 11:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What about inverting the message phrasing, ie
>> 
>> ERROR: type stuff must not be a table's row type

> It also can't be a view's row type, a sequence's row type, a foreign
> table's row type...

Well, you could say "relation's row type" if you wanted to be formally
correct, but I'm not convinced that's an improvement.

			regards, tom lane