From: Josh Berkus <josh@agliodbs.com>
To: elein <elein@varlena.com>
Cc: postgresql advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [SQL] SQL Spec Compliance Questions
Date: Fri, 4 Jun 2004 12:20:47 -0700
Message-ID: <200406041220.47452.josh@agliodbs.com> (raw)
In-Reply-To: <20040604113316.K11485@cookie.varlena.com>
References: <200403302050.12415.josh@agliodbs.com>
<200406031609.51415.josh@agliodbs.com>
<20040604113316.K11485@cookie.varlena.com>
Elein,
> In postgres and Illustra, references were possible.
> That is, storing the OID (REF) of a table in a column of another
> table achieving the same effect. SQL syntax support
> was needed for the REF type. I believe this was removed
> or suppressed in PostgreSQL.
Yeah, I'd like to see a return of table references as FKs. It would allow me
to eliminate all of these rather non-relational integer-based surrogate keys.
I don't think our OIDs would be the way to go on this, given the problems
already discussed with PG OIDs. I kinda like SyBase's solution, where they
have a system-acessable hash key of the data in the row.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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-sql@postgresql.org
Cc: josh@agliodbs.com, elein@varlena.com, pgsql-advocacy@postgresql.org
Subject: Re: [SQL] SQL Spec Compliance Questions
In-Reply-To: <200406041220.47452.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