Re: Why Oracle does not allow rollback of DDL statements?

From: Cristian Cudizio <cristian.cudizio_at_yahoo.it>
Date: Mon, 10 Nov 2008 03:59:05 -0800 (PST)
Message-ID: <d7af1c47-504e-4722-9fc1-df744024e815@q26g2000prq.googlegroups.com>


On 10 Nov, 10:02, Thomas Kellerer <YQDHXVLMU..._at_spammotel.com> wrote:
> Noons, 10.11.2008 09:45:
>
> >> I have always been surprised why Oracle does a implicit commit when
> >> DDL statements (e.g create table ) are executed.
>
> > It's called database consistency.
> > Only real databases have it.
>
> But creating objects in a database needs to be consistent as well. I don't see why having transactional DDL contradicts database consistency.
>
> Actually I think it adds to consistency.
>
> >> DDL statements
> >> simply write information (insert, delete and update) to data
> >> dictionary, so why DDL statement cannot be rolled back.
>
> > Oh no they most certainly don't just do that!
>
> So what else are they doing?
>

They allocate space on tablespaces (obviusly speaking about locally managed tablespaces)

Regards,

 Cristian Received on Mon Nov 10 2008 - 05:59:05 CST

Original text of this message