pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Rod Taylor <pg@rbt.ca>
Cc: Alexandre Leclerc <alexandre.leclerc@gmail.com>
Subject: Re: Data type to use for primary key
Date: Mon, 22 Nov 2004 22:00:41 -0800
Message-ID: <200411222200.41729.josh@agliodbs.com> (raw)
In-Reply-To: <1101171791.44437.7.camel@home>
References: <1dc7f0e30411221232603c4617@mail.gmail.com>
	<200411221654.56673.josh@agliodbs.com>
	<1101171791.44437.7.camel@home>

Rod,

> It would be nice if PostgreSQL had some form of transparent surrogate
> keying in the background which would automatically run around and
> replace your real data with SERIAL integers. It could use a lookup table
> for conversions between the surrogate and real values so the user never
> knows that it's done, a bit like ENUM. Then we could all use the real
> values with no performance issues for 1) because it's an integer in the
> background, and 2) because a cascade only touches a single tuple in the
> lookup table.

Sybase does this, and it's a feature I would dearly love to emulate.  You can 
just refer to another table, without specifying the column, as an FK and it 
will create an invisible hashed key.   This is the type of functionality Codd 
was advocating -- invisible, implementation-automated surrogate keys -- in 
the mid 90's (don't have a paper citation at the moment).

So you'd just do:

create table client_contacts (
	fname text not null,
	lname text not null,
	client foriegn key clients,
	position text,
	notes text
);

and the "client" column would create an invisible hashed key that would drag 
in the relevant row from the clients table; thus a:

select * from client_contacts

would actually show the whole record from clients as well.
	

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (14+ messages)  latest in thread

Message-ID: <200411222200.41729.josh@agliodbs.com>
Permalink:  ../200411222200.41729.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200411222200.41729.josh@agliodbs.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-performance@postgresql.org
  Cc: josh@agliodbs.com, pg@rbt.ca, alexandre.leclerc@gmail.com
  Subject: Re: Data type to use for primary key
  In-Reply-To: <200411222200.41729.josh@agliodbs.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