Re: ALTER TABLE schema SCHEMA TO new_schema? - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: ALTER TABLE schema SCHEMA TO new_schema?
Date
Msg-id 007f01c29a3d$f38ecda0$6500a8c0@internal
Whole thread Raw
In response to ALTER TABLE schema SCHEMA TO new_schema?  (Joe Conway <mail@joeconway.com>)
Responses Re: ALTER TABLE schema SCHEMA TO new_schema?
List pgsql-hackers
> Yeah, good point. I think properly dealing with the pg_depends issues will
> catch anything of that nature, but what to do with them?
>
> Probably should move dependent type, constraint, index entries to the same
new
> namespace. We might want to move related sequences, but I'm not sure we'd
want
> to do that silently, since the sequence could be in use for other tables
as
> well. And we should probably restrict the change if there are dependent
> functions or views. Does this capture the issues?

Why just restrict them to moving tables?  What if someone wants to move a
function or an aggregate to another schema?

What if they want to copy it?

Chris



pgsql-hackers by date:

Previous
From: Henner Zeller
Date:
Subject: PG 7.3: Query Meta Data with the JDBC-driver
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: toast table growing indefinitely? Known