Andrew Dunstan wrote:
I have a client who is looking for a way to be able to alter objects
without having to recreate (say, from a dump) all the objects in a
possibly large dependency tree rooted at the object. Of course, if the
alteration invalidates the dependency, than this operation should fail,
but adding a column to a view or table (which is our most common case)
should arguably be a benign operation that shouldn't fail because of
dependencies.
I couldn't see anything in the TODO list that seemed appropriate, in a
quick scan.
I don't follow you. I can currently add a column, without breaking
either foriegn keys or inheritance. What's the problem?
--Josh
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
