From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Imperfect solutions |
Date: | 2001-06-06 01:44:24 |
Message-ID: | ECEHIKNFIMMECLEBJFIGIEOGCAAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Those two points are already mentioned - I have another 90%
> patch ready to
> > go that will add that functionality as well...
>
> As a question, are you doing anything to handle dropping referenced unique
> constraints or are we just waiting on that until a referencing system
> is built?
By that do you mean: what happens when you drop a primary key that is
referenced by a foreign key?
My answer: Forgot about that ;) I'll see what I can do but anytime
investigation of foreign keys is required it's a real pain. Foreign keys
are kinda next on my list for work, so I might look at it then if it's too
difficult right now. (I've got a query that can find all foreign keys on a
relation, and what they relate to, that I'm going to add to psql).
My other questions then are:
Does anything else (other than fk's) ever reference a primary key?
What can reference a unique key?
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2001-06-06 01:58:05 | RE: Feature request : Remove identifier length constraints |
Previous Message | Severin Olloz | 2001-06-06 00:55:50 | ORDER BY Problem... |