From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: deleting dependencies |
Date: | 2003-02-20 15:09:21 |
Message-ID: | 22139.1045753761@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> I've been looking at the dependency API and I notice that there is a
> function to delete ALL dependencies on an object and a function to add a
> dependency, but there doesn't seem to be any way of deleting a dependency
> between two _particular_ objects.
In the ALTER cases that have been implemented so far, it seemed easiest
to wipe the full set of dependencies and then regenerate them from the
altered object. I think you will find the same is true of altering
column type. To take just one example, the column default expression
(if any) almost certainly has to be replaced too, and it may contain
dependencies.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-20 15:38:51 | Re: A bad behavior under autocommit off mode |
Previous Message | Tom Lane | 2003-02-20 14:58:05 | Re: request for sql3 compliance for the update command |