Composite datatypes, dynamic member fields

From: Robert Staudinger <r(dot)staudinger(at)seminarshop(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Composite datatypes, dynamic member fields
Date: 2002-05-10 09:48:46
Message-ID: 1021024137.4493.18.camel@ws224
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

Hello,

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".
Ok this may be completely insane but ...

Maybe you could just tell me if it's worth to dig deeper.

Robert Staudinger

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Robert Staudinger 2002-05-10 09:51:51 Composite datatypes, dynamic member fields
Previous Message Iavor Raytchev 2002-05-10 08:58:28 internal voting