Re: ALTER TABLE schema SCHEMA TO new_schema?
| От | Christopher Kings-Lynne |
|---|---|
| Тема | Re: ALTER TABLE schema SCHEMA TO new_schema? |
| Дата | |
| Msg-id | 007f01c29a3d$f38ecda0$6500a8c0@internal обсуждение исходный текст |
| Ответ на | ALTER TABLE schema SCHEMA TO new_schema? (Joe Conway <mail@joeconway.com>) |
| Ответы |
Re: ALTER TABLE schema SCHEMA TO new_schema?
|
| Список | 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 по дате отправления: