2010/10/25 Robert Haas <robertmh...@gmail.com>: > On Mon, Oct 25, 2010 at 3:11 PM, Peter Eisentraut <pete...@gmx.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? Regards Pavel > > 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: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
