pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Bitmead <chris@bitmead.com>
To: Hannu Krosing <hannu@tm.ee>
Cc: Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Thus spoke SQL3 (on OO)
Date: Tue, 23 May 2000 06:04:19 +1000
Message-ID: <392992C3.9DFC0F31@bitmead.com> (raw)
References: <Pine.LNX.4.21.0005201507330.423-100000@localhost.localdomain>
	<00052104000003.14806@comptechnews>
	<392830DA.B5546EF7@bitmead.com>
	<00052108053904.14806@comptechnews>
	<39286B3F.F4594E40@bitmead.com>
	<39283008.ED83E94@tm.ee>
	<39287873.D023D7E5@nimrod.itg.telecom.com.au>
	<3928F01B.B0C6D563@tm.ee>
	<39298E29.16B280CC@bitmead.com>
	<3928F748.3F51EA87@tm.ee>

Hannu Krosing wrote:

> it would be hard to define RI by just saying that some field references "an
> OID",
> often you want to be able do define something more specific.
> 
> It would be too much for most users to require that all primary and foreign
> keys
> must be of type OID.

Since it would be object and relational, you could do either. But all
pure object databases _always_ rely on oid to define relationships, and
that is likely to be all an ODMG inteface would support. Unless we want
to break new ground anyway.



view thread (23+ messages)

Message-ID: <392992C3.9DFC0F31@bitmead.com>
Permalink:  ../392992C3.9DFC0F31@bitmead.com/
Also on:    postgresql.org/message-id/392992C3.9DFC0F31@bitmead.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: chris@bitmead.com, hannu@tm.ee, chrisb@nimrod.itg.telstra.com.au
  Subject: Re: Thus spoke SQL3 (on OO)
  In-Reply-To: <392992C3.9DFC0F31@bitmead.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox