Re: Transactional DDL - Mailing list pgsql-general

From Harpreet Dhaliwal
Subject Re: Transactional DDL
Date
Msg-id d86a77ef0706020946l3c334982u8dd80ad00fc15ec1@mail.gmail.com
Whole thread Raw
In response to Re: Transactional DDL  ("Dawid Kuroczko" <qnex42@gmail.com>)
Responses Re: Transactional DDL  (Ron Johnson <ron.l.johnson@cox.net>)
List pgsql-general
So, while writing any technical document, would it be wrong to mention stored procedures in postgresql?
what is the general convention?

On 6/2/07, Dawid Kuroczko <qnex42@gmail.com> wrote:
On 6/2/07, Jasbinder Singh Bali < jsbali@gmail.com> wrote:
> 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

Actually, Oracle inserts implicit COMMIT after each DDL.

So, if you have:

BEGIN;
INSERT INTO foo (bar) VALUES (1);
CREATE INDEX foo_bar ON foo (bar);
-- Here Oracle will insert implicit COMMIT, thus your foo table will
have value 1 commited.
-- And here Oracle will BEGIN a new trasaction.
INSERT INTO foo (bar) VALUES (2);
ROLLBACK;
-- And you will rollback the insert of value 2.  Value 1 remains in the table,
-- because it is already committed.

   Regards,
       Dawid

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org/

pgsql-general by date:

Previous
From: Erwin Brandstetter
Date:
Subject: Re: There can be only one! How to avoid the "highlander-problem".
Next
From: Jeremy Harris
Date:
Subject: Re: why postgresql over other RDBMS