| From: | PFC <lists(at)peufeu(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jaime Casanova" <systemguards(at)gmail(dot)com> |
| Cc: | "Harpreet Dhaliwal" <harpreet(dot)dhaliwal01(at)gmail(dot)com>, "Jasbinder Singh Bali" <jsbali(at)gmail(dot)com>, "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, "Alexander Staubo" <alex(at)purefiction(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Transactional DDL |
| Date: | 2007-06-03 07:41:58 |
| Message-ID: | op.ttb4z80gcigqcu@apollo13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 03 Jun 2007 01:39:11 +0200, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
>> Tom's example seems to show that mysql inserts a commit immidiatelly
>> after a DDL but this one example shows the thing is worse than that.
>
> Actually, I think their behavior is just "DDL issues a COMMIT", so that
> after that you are out of the transaction and the INSERT commits
> immediately. Some experimentation shows that mysql doesn't issue a
> warning for rollback-outside-a-transaction, so the lack of any complaint
> at the rollback step is just standard mysql-ism.
Yes, their manual explains this and warns against it. The full list is
here :
http://www.mysql.org/doc/refman/5.1/en/implicit-commit.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Badawy, Mohamed | 2007-06-03 08:34:47 | general features |
| Previous Message | Pavel Stehule | 2007-06-03 06:16:56 | Re: Turning on logging |