Skip site navigation (1) Skip section navigation (2)

Re: foreign keys for array/period contains relationships

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: foreign keys for array/period contains relationships
Date: 2010-10-25 20:10:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
2010/10/25 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Mon, Oct 25, 2010 at 3:11 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> Currently, foreign keys only work with the = operator (the name might be
>> different, but it needs to behave like equality).  I'm thinking there
>> are other scenarios that could be useful, for example with arrays and
>> range types.
>> Example #1: Foreign key side is an array, every member must match some
>> PK.
>> CREATE TABLE pk (a int PRIMARKY KEY, ...);
>> CREATE TABLE fk (x int[] REFERENCES pk (a), ...);

What about optimalizations and planning? This is classic sample how
don't use a arrays?



> I've wished for this before when doing app dev with PG.  I think it
> would be pretty neat.  The other cases seem potentially useful, too,
> but especially this one.
> --
> Robert Haas
> EnterpriseDB:
> The Enterprise PostgreSQL Company
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:

In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2010-10-25 20:10:48
Subject: Re: ask for review of MERGE
Previous:From: Tom LaneDate: 2010-10-25 20:09:20
Subject: Re: Floating-point timestamps versus Range Types

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group