you can use SET TRANSACTION LEVEL READ UNCOMMITTED to acquire the dirty
reads
From your perspective how *should* the DB handle this?
M
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Jan de Visser" <jdevisser@digitalfairway.com>
To: <pgsql-general@postgresql.org>
Cc: "Harpreet Dhaliwal" <harpreet.dhaliwal01@gmail.com>; "Scott Marlowe"
<scott.marlowe@gmail.com>
Sent: Wednesday, August 15, 2007 5:15 AM
Subject: Re: [GENERAL] Transactional DDL
> 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.marlowe@gmail.com> wrote:
>> > On 8/14/07, Harpreet Dhaliwal <harpreet.dhaliwal01@gmail.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
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>