From: Hannu Krosing <hannu@tm.ee>
To: Chris Bitmead <chris@bitmead.com>
Cc: Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: Thus spoke SQL3 (on OO)
Date: Mon, 22 May 2000 12:38:57 +0300
Message-ID: <39290031.EFB912F7@tm.ee> (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>
<392992C3.9DFC0F31@bitmead.com>
Chris Bitmead wrote:
>
> 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.
Is the ODMG interface available on the net, or is the plan to do a Poet clone
?
> Unless we want to break new ground anyway.
We would need some syntax to distinguish between REFERENCES (primary key) and
REFERENCES (oid).
Of course we would also need fast lookups by oid and oid->object lookup
tables(s)/function(s) but that's another part of the story.
--------------
Hannu
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: hannu@tm.ee, chris@bitmead.com, chrisb@nimrod.itg.telstra.com.au
Subject: Re: Thus spoke SQL3 (on OO)
In-Reply-To: <39290031.EFB912F7@tm.ee>
* 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