Josh Berkus wrote:
> Hackers,
>
> We need to update the SoC page:
> http://www.postgresql.org/developer/summerofcode
>
> ... with new ideas and projects appropriate for PostgreSQL 8.4/8.5.
> Please make suggestions. Thanks!
>
> --Josh
>
On last year's summer of code page,
http://www.postgresql.or
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
Wouldn't
ALTER [OBJECT] RENAME TO [schema.][name]
be a better?
After all, this is essentially a rename operation,
so maybe it is better to extend existing syntax...
5WD-02-Foundation-2003-09.pdf doesn't seem
to specify any renaming with ALTER TABLE...
---(end of broa
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
>> Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
>>> ... people want to be able to grant on all objects in a
>>> database, etc:
For things like this I use simple,
but super-powerful eval function:
CREATE OR REPLACE FUNCTION eval(text)
RETURNS
Hello!
The following SQL works:
ALTER TABLE a.foo RENAME TO bar;
But the following doesn't:
ALTER TABLE a.foo RENAME TO b.bar;
The capability to move objects to other schemas
would be quite useful.
Apparently, everything works OK if you change
pg_class.relnamespace with UPDATE, but this is
no
