| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE schema SCHEMA TO new_schema? |
| Date: | 2002-12-01 05:47:53 |
| Message-ID: | 15899.1038721673@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> writes:
> Someone asked earlier about how to change a bunch of existing tables int the
> PUBLIC schema to some other schema. For grins I tried:
> regression=# update pg_class set relnamespace=556829 where relname = 'foo' and
> relnamespace=2200;
> UPDATE 1
> and it seemed to work fine (i.e. moved foo from schema public to schema bar).
But it didn't fix the pg_depend entries linking the table to its schema :-(
> But it made me wonder if we shouldn't have:
> ALTER TABLE table SCHEMA TO new_schema
I was thinking more along the lines of ALTER TABLE a.b RENAME TO x.y
I don't see anything in the SQL spec about this; anyone know what
precedent is in Oracle or other DBMSes?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-01 05:55:14 | Re: 7.4 Wishlist |
| Previous Message | Joe Conway | 2002-12-01 05:32:22 | Re: Segmentation fault while COPY in 7.3 |