pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: postgresql advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [SQL] SQL Spec Compliance Questions
Date: Thu, 3 Jun 2004 19:19:06 +0200
Message-ID: <20040603171905.GI32598@nibiru.metux.de> (raw)
In-Reply-To: <1129.1080928076@sss.pgh.pa.us>
References: <200403302050.12415.josh@agliodbs.com>
	<406D1031.7010603@joeconway.com>
	<200404020838.22698.josh@agliodbs.com>
	<406D9943.8070401@joeconway.com>
	<1129.1080928076@sss.pgh.pa.us>

* Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Joe Conway <mail@joeconway.com> writes:
> >>> 4.16.2 Referenceable tables, subtables, and supertables
> >>> A table BT whose row type is derived from a structured type ST is
> >>> called a typed table. Only a base table or a view can be a typed
> >>> table. A typed table has columns corresponding, in name and
> >>> declared type, to every attribute of ST and one other column REFC
> >>> that is the self-referencing column of BT; let REFCN be the
> 
> > After re-reading it, I think it is related to (or at least similar to) 
> > the work Tom is currently doing to allow composite types as table 
> > attributes.
> 
> The "structured type" stuff seems closely related, but I do not
> understand the business about a "self-referencing column".  I have a
> feeling that it might be a mutant version of our notion of inheritance
> ...

hmm, for some moments I thought on things like the OID attribute
(on "system generated attrs")

Who we could ask to explain that ?!

cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     contact@metux.de
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------



view thread (19+ messages)  latest in thread

Message-ID: <20040603171905.GI32598@nibiru.metux.de>
Permalink:  ../20040603171905.GI32598@nibiru.metux.de/
Also on:    postgresql.org/message-id/20040603171905.GI32598@nibiru.metux.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: weigelt@metux.de, pgsql-advocacy@postgresql.org
  Subject: Re: [SQL] SQL Spec Compliance Questions
  In-Reply-To: <20040603171905.GI32598@nibiru.metux.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox