| From: | "Emils Klotins" <emils(at)grafton(dot)lv> |
|---|---|
| To: | Michael Teter <michael_teter(at)yahoo(dot)com> |
| Cc: | pgsql-sql(at)hub(dot)org |
| Subject: | Re: renaming columns... danger? |
| Date: | 2000-10-27 09:00:27 |
| Message-ID: | 39F9604B.10625.28D2CFDA@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Subject: [SQL] renaming columns... danger?
> I just discovered that doing an alter table ... alter
> column (to rename a column) does not do a complete
> rename throughout the database.
> shouldn't rename update any index and key definitions?
> I'm very frightened right now, because I'm rather
> dependent upon my database right now. I don't like
> the thought that my database is corrupt at the schema
> level.
>
Yes, I believe the same is true about trigger definitions and
suchlike.
In short - to do a rename on column I do a pg_dumpall and change
all references of the name by hand :*(((
Btw, is there a way to see what triggers are defined for particular
field? Or how to drop triggers, which (by default) are unnamed?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-10-27 10:43:52 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| Previous Message | Grant Finnemore | 2000-10-27 08:30:19 | Re: [SQL] renaming columns... danger? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clayton C. | 2000-10-27 11:36:04 | benchmarks |
| Previous Message | Grant Finnemore | 2000-10-27 08:30:19 | Re: [SQL] renaming columns... danger? |