| From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transactional DDL |
| Date: | 2007-06-02 18:55:27 |
| Message-ID: | 4661BD1F.5090005@cox.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 06/02/07 13:35, Jasbinder Singh Bali wrote:
> On 6/2/07, Michael Glaesemann <grzm(at)seespotcode(dot)net> wrote:
>>
>>
>> On Jun 2, 2007, at 11:08 , Harpreet Dhaliwal wrote:
>>
>> > Whats so novel about postgresql here?
>> > This would happen in any RDBMS. right?
>> > You induced divide by zero exception that crashed the whole
>> > transaction and it did not create the table bar?
>>
>> [Please don't top-post. It makes the discussion hard to follow.]
>>
>> I used the divide by zero to raise an error to show that both the
>> CREATE TABLE and the INSERT were rolled back when the transaction
>> failed. If there's another definition of transactional DDL, I'd like
>> to know what it is.
>>
>> Michael Glaesemann
>> grzm seespotcode net
>
>
> This is what happens in every RDBMS. Whats so special about postgres then?
But it's NOT what happens in every RDBMS. Oracle implicitly
executes a COMMIT after every DDL statement.
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paolo Bizzarri | 2007-06-02 19:11:43 | Re: Corruption of files in PostgreSQL |
| Previous Message | Russ Brown | 2007-06-02 18:52:54 | Re: Transactional DDL |