Received: from tech.com.au (IDENT:root@techpt.lnk.telstra.net
 [139.130.75.122])
	by hub.org (8.9.3/8.9.3) with ESMTP id GAA95941
	for <pgsql-hackers@postgresql.org>;
	Mon, 22 May 2000 06:04:43 -0400 (EDT)
	(envelope-from chris@bitmead.com)
Received: from bitmead.com (IDENT:chris@tardis [203.41.180.243])
	by tech.com.au (8.9.3/8.9.3) with ESMTP id UAA08355;
	Mon, 22 May 2000 20:04:23 +1000
Message-ID: <392992C3.9DFC0F31@bitmead.com>
Date: Tue, 23 May 2000 06:04:19 +1000
From: Chris Bitmead <chris@bitmead.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Hannu Krosing <hannu@tm.ee>
CC: Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Thus spoke SQL3 (on OO)
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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200005/442

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.