Re: Request for Comments: ALTER [OBJECT] SET SCHEMA - Mailing list pgsql-hackers

From ziga@mail.ljudmila.org
Subject Re: Request for Comments: ALTER [OBJECT] SET SCHEMA
Date
Msg-id 52983.193.77.186.68.1118325838.squirrel@webmail.ljudmila.org
Whole thread Raw
In response to Re: Request for Comments: ALTER [OBJECT] SET SCHEMA  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-hackers
What about:

ALTER [OBJECT] RENAME TO [schema.]name [CASCADE]

This has somewhat less new syntax.
CASCADE would also move dependant objects.

Perhaps trigger functions should not be moved, since it
is not really obvious how to do this right.
Warning should be issued in this case.

Command basically frees user from having to hack system
castalogs; Is moving dependant object really such a big deal?
PostgreSQL does not really care where they are and just
keeps working - maybe this should be left up to DBA.




pgsql-hackers by date:

Previous
From: "Arshad Mahmood"
Date:
Subject: Building WIN32 DLL's
Next
From: "Jim C. Nasby"
Date:
Subject: Re: [GENERAL] mirroring oracle database in pgsql