From: | Chris Bitmead <chris(at)bitmead(dot)com> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: ORDBMS |
Date: | 2000-01-31 00:13:35 |
Message-ID: | 3894D3AF.F335EB78@bitmead.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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...
I think the idea is like in C++ if you create a
class Address {
...
}
and a class
class Person {
Address address;
}
Then you can create both standalone Addresses as well as addresses
embedded
inside the Person.
CREATE DATATYPE might be a thought, but it's probably not very
essential.
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-01-31 00:32:19 | Re: [HACKERS] Re: ORDBMS |
Previous Message | Chris Bitmead | 2000-01-31 00:11:12 | Re: [HACKERS] Re: ORDBMS |