From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bill MacArthur <webmaster(at)dhs-club(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: table row type and query-specified row type do not match |
Date: | 2012-03-08 21:25:51 |
Message-ID: | 7576.1331241951@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Bill MacArthur <webmaster(at)dhs-club(dot)com> writes:
> Perhaps this issue has been resolved in higher sub-versions or in 9.1?
No, seems to be just the same in HEAD :-(
> In summary, the issue revolves around the data type of a column being changed, but the data type in a dependent rule on another table does not. Does the data type have to be embedded in the rule?
Yeah, it does, or at least the implications of not doing so would amount
to a ground-up redesign, as well as moving a lot of cycles out of rule
creation and into every rule use.
What I would have expected to happen is for the ALTER TABLE to throw an
error telling you it couldn't cope with updating the rule, and that
you'd need to fix that manually. There is such a test involving views;
not sure why it's not catching this rule.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2012-03-08 22:41:14 | Re: Extension tracking temp table and causing update failure |
Previous Message | Bill MacArthur | 2012-03-08 20:20:13 | table row type and query-specified row type do not match |