Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly
От | Robert Haas |
---|---|
Тема | Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly |
Дата | |
Msg-id | 603c8f070912100909j2f10fcd6xc92fbaa9234316bb@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view
definition incorrectly
|
Список | pgsql-bugs |
On Thu, Dec 10, 2009 at 11:57 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Andrew Gierth <andrew@tao11.riddles.org.uk> writes: >> There's another possible solution (albeit a somewhat nontrivial one) >> which came up when a bunch of us were talking about this one on IRC; >> which is to handle the problem in the view deparse: if a column used >> in a USING clause has been renamed, add an alias to the query that >> renames it back, e.g. >> =A0 select ... from table1 as table1(v,a) join ... using (v) > > Hmm. =A0Cute, 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. ...Robert
В списке pgsql-bugs по дате отправления: