Re: Transactional DDL - Mailing list pgsql-general

From Jasbinder Singh Bali
Subject Re: Transactional DDL
Date
Msg-id a47902760706020812q7867948cv37dbcf228a5627c4@mail.gmail.com
Whole thread Raw
In response to Re: Transactional DDL  ("Alexander Staubo" <alex@purefiction.net>)
Responses Re: Transactional DDL  (Michael Glaesemann <grzm@seespotcode.net>)
Re: Transactional DDL  ("Dawid Kuroczko" <qnex42@gmail.com>)
List pgsql-general
But its said that transactions in any RDBMS follow ACID properties.
So if i put a create table and an Insert statement in the same begin end block as one single transactioin, won't both create and insert follow acid property, being in one single trasaction, and either both get committed or none, talking about oracle lets say

On 6/2/07, Alexander Staubo <alex@purefiction.net> wrote:
On 6/2/07, Jasbinder Singh Bali <jsbali@gmail.com> wrote:
[snip]
> I believe that if a database supports transactional ddl then ddl1 and ddl2
> would commit together as a batch
> And
> If a Db doesn't support this transactional DDL feature then ddl1 executes
> and commits without even caring about ddl2. Right?

Exactly right -- Oracle, for example, implicitly commits the
transaction when you execute a DDL statement such as "create table".

Alexander.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Corruption of files in PostgreSQL
Next
From: Michael Glaesemann
Date:
Subject: Re: Transactional DDL