Re: [HACKERS] Re: ORDBMS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: ORDBMS
Date
Msg-id 9839.949040200@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: ORDBMS  (Chris Bitmead <chris@bitmead.com>)
Responses Re: [HACKERS] Re: ORDBMS
List pgsql-hackers
Chris Bitmead <chris@bitmead.com> writes:
> Tom Lane wrote:
>> For a lot of this older stuff, there isn't even any documentation
>> (that I know of) on what it's *supposed* to do, let alone on how
>> thorough the original implementation was.

> I thought that the original berkeley doco covered this to some extent.

Where would I find that?

> Basicly I think you're supposed to be able to go...

> CREATE TABLE address (street TEXT, number TEXT, suburb TEXT, zip TEXT);
> CREATE TABLE person (name TEXT, address ADDRESS);

> SELECT name, address FROM person WHERE person.address.suburb = 'New
> York';

Hmm.  This looks like a CREATE TABLE implicitly creates a datatype
that acts more or less like a C 'struct' declaration, ie, it's just a
collection of subfields.  OK, a struct-making declaration is certainly
useful.  What I don't understand yet is whether the contents of table
"address" have any connection to the data stored in table "person".
If not, why must I create a table in order to define a datatype?  Seems
like a separate CREATE DATATYPE command would make more sense...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] [6.5.2] potentially major bug?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] ONLY vs "*"