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: Mon, 22 May 2000 21:18:25 +1000
Message-ID: <39291781.D9947450@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>
	<392992C3.9DFC0F31@bitmead.com>
	<39290031.EFB912F7@tm.ee>

Hannu Krosing wrote:

> Is the ODMG interface available on the net, or is the plan to do a Poet > clone

Looking at database vendor specs will get us a fair way. Or you can
shell the $35 for a spec.

> > Unless we want to break new ground anyway.
> 
> We would need some syntax to distinguish between REFERENCES (primary 
> key) and REFERENCES (oid).

The trouble is the client cache code is generally all set up to cache by
oid. If you want to start referencing objects by various criteria, the
client cache becomes a lot more complex. More inefficient too because
you would have to set up hash tables on multiple criteria and jump
between them.

It's not such a big deal really. When you do an OO model you don't need
to think about your own primary key.

> 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.

An index on oid will be a start.

-- 
Chris Bitmead
mailto:chris@bitmead.com
http://www.techphoto.org - Photography News, Stuff that Matters



view thread (23+ messages)  latest in thread

Message-ID: <39291781.D9947450@bitmead.com>
Permalink:  ../39291781.D9947450@bitmead.com/
Also on:    postgresql.org/message-id/39291781.D9947450@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: <39291781.D9947450@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