Re: is CREATE TABLE not transactional?
Darren Duncan <[email protected]>
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <p06230903c01c153b8925@[192.168.1.101]> |
At 5:13 PM -0600 2/16/06, Paul DuBois wrote: >>Is CREATE TABLE not protected by transactions in MySQL? I just tried doing >>this: > >See: > >http://dev.mysql.com/doc/refman/5.0/en/implicit-commit.html From the above-linked page: Each of the following statements (and any synonyms for them) implicitly end a transaction, as if you had done a COMMIT before executing the statement: ... Transactions cannot be nested. This is a consequence of the implicit COMMIT performed for any current transaction when you issue a START TRANSACTION statement or one of its synonyms. I think that's something which needs to be fixed. Nothing except an explicit COMMIT should cause a commit, and nested transactions should be supported. Doing so would greatly improve MySQL's reliability and make it easier to use. A good time to implement this would be for 5.1, or 5.2 if 5.1 is now trying to stabilize. -- Darren Duncan -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]