Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Oh, you bring up two important issues --- one is is the gap in time
> between the drop and the recreate. This case can be done by
> doing the query in a transaction --- the lock will exist until the
> transaction completes, and in fact, you can roll it back in case you
> don't like it.
IIRC, Oracle does not have rollback-able DDL. That might imply that the
reason they have MODIFY CONSTRAINT is that in Oracle you can't use the
above way to eliminate the window. Can you put ALTERs inside
transactions at all in Oracle?
regards, tom lane
