| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [SQL] SQL Spec Compliance Questions |
| Date: | 2004-04-02 17:47:56 |
| Message-ID: | 1129.1080928076@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-sql |
Joe Conway <mail(at)joeconway(dot)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
...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-04-02 18:57:41 | Re: PITR for replication? |
| Previous Message | Marc G. Fournier | 2004-04-02 17:15:41 | Re: Aberdeen Study on OS RDBMS: exceprts and |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregor Rot | 2004-04-03 15:08:34 | Re: order of results |
| Previous Message | Josh Berkus | 2004-04-02 16:53:04 | Re: SQL Spec Compliance Questions |