Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA10006; Tue, 16 Mar 93 02:02:00 -0800
Date: Tue, 16 Mar 93 02:02:00 -0800
Message-Id: <9303161002.AA10006@postgres.Berkeley.EDU>
From: mueller@n1.imsd.uni-mainz.DE (Robert Mueller)
Subject: OO-features of postgres
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu


Hi,

we are developing an OO-application (using Objective C) and are now thinking about a OO-database. So I would like to hear about your experiences with the OO-features of Postgres. Is it difficult to store complex objects to the postgres backend? (I do not want to define "complex" in common, think - for example - of an object with a list of lists of lists in it's datastructure, and each list has a dynamic length...)

Some authors say, Postgres is not really an Object-Oriented database, but an extended relational database ... (IEEE Computer, Feb. 93, Page 49). What about this?

Your e-mail are welcome

R. Mueller
University of Mainz
Germany