| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: alter table alter columns vs. domains |
| Date: | 2004-05-06 17:43:58 |
| Message-ID: | 1083865438.91282.26.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2004-05-06 at 13:23, Merlin Moncure wrote:
> > Yes. This is something I was going to look at doing in the next
> release.
>
> Quick question:
> With your potential changes, you would then be able to alter a domain
> that is involved in RI constraints between 2 or more tables without
> bringing down the constraints, yes? This would be great :)
I had been hoping to get away without actually rechecking foreign key
constraints, as that makes it significantly more complicated -- but if
you set the value to NULL then problems could arise (otherwise fkeys
would still match so long as UNIQUE wasn't violated).
We would need to apply phases 1 to 3 on all of the tables and move
foreign key checks to a phase 4 (intertable work phase?)
In the mean time, you can create a new domain then modify the type of
all the tables.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2004-05-06 17:46:16 | Re: alter table alter columns vs. domains |
| Previous Message | Merlin Moncure | 2004-05-06 17:23:37 | Re: alter table alter columns vs. domains |