From: | Robert Staudinger <robert(dot)staudinger(at)fh-sbg(dot)ac(dot)at> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Composite datatypes, dynamic member fields |
Date: | 2002-05-12 10:10:26 |
Message-ID: | 200205121010.MAA11603@mx0.int.fh-sbg.ac.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> I use inheritance in such a case.
> (see INHERITS in CREATE TABLE)
> Table with common columns as a base class
> and different tables for classes with
> inherited base class.
> Multiple and multilevel inheritanse possible.
The problem in my case is that even a group of objects which belong
together might not have even one common attributes.
One idea is to implement a . operator on a basic data type and return the value
for the corresponding field from the "operator function".
E.g.
"select * from TABLE where mytype.mymember='x'"
could call something like
mytype_member_access( mytype, member_name )
Unfortunately I don't have any idea how to handle updates on fields yet.
Does anybody have any advice on that?
Robert Staudinger
PS: Please excuse if this explanation doesn't make much sense to you -
it's a little hard for me to say in English what I
mean.
From | Date | Subject | |
---|---|---|---|
Next Message | Bartus Levente | 2002-05-12 10:15:37 | Re: [HACKERS] internal voting |
Previous Message | Peter Eisentraut | 2002-05-12 09:23:29 | Re: PgAccess directory structure |