| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Leon <leon(at)udmnet(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Simms <grim(at)argh(dot)demon(dot)co(dot)uk>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] DROP TABLE inside transaction block |
| Date: | 1999-09-06 18:29:20 |
| Message-ID: | 37D40800.D3E07EE1@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Leon wrote:
>
> Tom Lane wrote:
>
> >
> > In short, a lot of work for a very marginal feature. How many other
> > DBMSes permit DROP TABLE to be rolled back? How many users care?
> >
>
> Don't know. But here is the idea: drop table rollback is needed in
> automation of DB restructuring.
Actually the underlying mechanics could be used for other things too,
like:
ALTER TABLE DROP COLUMN colname, or even changing the type of column,
say
from int4 -> int8 -> float -> char -> varchar -> text ?
I know that Oracle at least allows the latter but I'm not sure how
it does that
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yu Cao | 1999-09-06 23:39:27 | Re: [HACKERS] PostgreSQL 6.5.1: libpq++ libraries on IRIX 6.5 |
| Previous Message | Hannu Krosing | 1999-09-06 17:21:02 | Troubles from using pg_dumpall with dbname |