From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
Date: | 2006-06-30 21:35:30 |
Message-ID: | 60odwauy1p.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-www |
ron(dot)l(dot)johnson(at)cox(dot)net (Ron Johnson) writes:
> Scott Marlowe wrote:
> [snip]
>> However, the more interesting thing here, is that every
>> statement, including DDL is transactable, except for a couple of
>> big odd ones, like create database. So, in postgresql, you can do:
>>
>> begin;
>> create table xyz...
>> alter table abc...
>> insert into abc select * from iii
>> update iii...;
>> drop table iii;
>> (oops, I messed up something)
>> rollback;
>
> But isn't that what it means to be "transactional"? Or am I spoiled
> by my "big, expensive enterprise database"?
DDL commonly hasn't been "able to be rolled back," even in "big,
expensive" databases...
--
(format nil "~S(at)~S" "cbbrowne" "cbbrowne.com")
http://www.ntlug.org/~cbbrowne/unix.html
Rules of the Evil Overlord #180. "If I ever build a device to transfer
the hero's energy into me, I will make sure it cannot operate in
reverse." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-06-30 22:16:46 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
Previous Message | Chris Browne | 2006-06-30 21:34:40 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2006-06-30 22:16:46 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |
Previous Message | Chris Browne | 2006-06-30 21:34:40 | Re: Notes on converting from MySQL 5.0.x to PostgreSQL |