Re: Re-create dependent views on ALTER TABLE ALTER COLUMN ... TYPE?
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, ash <ash@commandprompt.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2014-06-02T17:43:01Z
Lists: pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > I agree, but I think it's important to note that Alex's complaint is > > not unique - the way things work now is a real source of frustration > > for users. > > Oh, I quite agree with that. My concern here has to do with automatically > and silently making changes that we can't be very sure will meet the > user's expectations. Perhaps what we need is some kind of UI/API design > whereby the user can inspect/modify/approve the semantic changes in > advance of pushing the red button. No clue how we'd manage to do that with just core, but could we provide something which would make it easier for pgAdmin-or-similar to do that? We could at least spit out NOTICE's and then see if the user decides to commit the change but I'm not sure how well that'd really work. In general, I like the idea.. Thanks, Stephen
Commits
-
Allow CREATE OR REPLACE VIEW to add columns to the _end_ of the view.
- ff1ea2173a92 8.4.0 cited