Re: is CREATE TABLE not transactional?

Darren Duncan <[email protected]> wrote:
> 	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.

	+1. No, +1,000.

	Being able to use FOR in triggers would be nice too! Cursors are a
pain in the butt. Not to mention being able to do a DELETE query with a
sub-select in the same table. Sometimes a WHERE clause just isn't enough to
convey what you want gone.

	I'm trying my best to keep supporting MySQL in my modules, but I'm
using Postgres on any new personal projects for the time being mainly
because of nusiances like this.

		- Tyler


-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]