| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Sergey Burladyan <eshkinkot(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly |
| Date: | 2009-12-10 18:03:39 |
| Message-ID: | 603c8f070912101003t67a36a53y3b2285c582d5b5b7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Dec 10, 2009 at 1:02 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Robert Haas escribió:
>> On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> > Hmm. Cute, but I wonder why we shouldn't just be throwing an error.
>> > As I said last night, the only thing I see wrong with the current
>> > behavior is that the error message isn't phrased in a way that makes
>> > it obvious it's the user's fault.
>>
>> I think the problem we're trying to solve is that the view works but
>> it isn't dumpable.
>
> So it would also be a solution that the ALTER TABLE that renamed the
> column throwed an error if there's a view that requires the name.
Yes. I don't think it's as good of a solution, but it is a solution.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Recursive complex query | 2009-12-10 18:27:47 | BUG #5239: Recursive complex query |
| Previous Message | Alvaro Herrera | 2009-12-10 18:02:43 | Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly |