From: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | "Harpreet Dhaliwal" <harpreet(dot)dhaliwal01(at)gmail(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Subject: | Re: Transactional DDL |
Date: | 2007-08-15 09:15:07 |
Message-ID: | 200708150515.07933.jdevisser@digitalfairway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday 15 August 2007 1:58:07 am Harpreet Dhaliwal wrote:
> So you mean to say something like this as far as oracle is concerned:
>
> BEGIN
> DDL 1 (commits right after its execution)
> DDL 2 (commits right after its execution)
> END
>
> That means there's no concept of putting DDL statements in a transaction in
> oracle basically, right?
Even worse: In certain transaction isolation levels (READ COMMITTED and
SERIALIZABLE IIRC) it yells at you and doesn't perform the DDL command.
Which makes it virtually impossible to do dynamic DDL in any serious J2EE
application.
<rant>
God, how I hate Oracle.
</rant>
>
> Thanks,
> ~Harpreet
jan
>
> On 8/15/07, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> > On 8/14/07, Harpreet Dhaliwal <harpreet(dot)dhaliwal01(at)gmail(dot)com> wrote:
> > > So you mean to say DDL statements can't be put in one single
> > > transaction
> >
> > in
> >
> > > Oracle ?
> >
> > You can put them in, but then they will cause the previous DMK to be
> > silently committed
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Staubo | 2007-08-15 09:32:23 | Re: Transactional DDL |
Previous Message | Hannes Dorbath | 2007-08-15 09:08:47 | Re: Persistent connections in PHP |