Skip site navigation (1) Skip section navigation (2)

Re: Composite datatypes, dynamic member fields

From: "(dot)"(at)babolo(dot)ru
To: r(dot)staudinger(at)seminarshop(dot)com (Robert Staudinger)
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Composite datatypes, dynamic member fields
Date: 2002-05-10 20:17:23
Message-ID: 200205102017.AAA15662@aaz.links.ru (view raw or flat)
Thread:
Lists: pgsql-interfaces
Robert Staudinger writes:
> I'm planning to build some kind of simple object oriented database and
> came across PostgreSQL because of it's nearly unlimited ways of
> extensibility.
> The documentation is really good an I learned a lot about composite
> datatypes, how to program them in c, create indices ... from the "Server
> Programming" section of the "Developer Manual".
> The problem in my case is that I don't know the names of the attributes
> beforehand so I can't do a table bases mapping with one table for each
> type of object ("class"). So I thought It would maybe be possible to
> store the objects always in the same composed datatype - with "dynamic
> member fields".
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.

> Ok this may be completely insane but ...
> 
> Maybe you could just tell me if it's worth to dig deeper.
> 
> Robert Staudinger
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html
> 


-- 
@BABOLO      http://links.ru/

In response to

Responses

pgsql-interfaces by date

Next:From: Peter EisentrautDate: 2002-05-10 21:24:40
Subject: Re: internal voting
Previous:From: Jim BoweryDate: 2002-05-10 16:07:38
Subject: dbconnect Argument Format?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group