From: | "Jasbinder Singh Bali" <jsbali(at)gmail(dot)com> |
---|---|
To: | "Alexander Staubo" <alex(at)purefiction(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transactional DDL |
Date: | 2007-06-02 15:12:44 |
Message-ID: | a47902760706020812q7867948cv37dbcf228a5627c4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)purefiction(dot)net> wrote:
>
> On 6/2/07, Jasbinder Singh Bali <jsbali(at)gmail(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lew | 2007-06-02 15:24:07 | Re: Delete with subquery deleting all records |
Previous Message | Lew | 2007-06-02 15:12:00 | Re: Faster data type for one-length values |