From: Peter Rabbitson <ribasushi@cpan.org>
Date: Tue, 26 May 2009 18:49:49 +0000 (+0000)
Subject: fix comments
X-Git-Tag: v0.08103~2
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ab807c129724c2be1ce02acf8a5c8f68d149421d;p=dbsrgits%2FDBIx-Class.git

fix comments
---

diff --git a/lib/DBIx/Class/Storage/DBI.pm b/lib/DBIx/Class/Storage/DBI.pm
index 0b244d4..eeb29c6 100644
--- a/lib/DBIx/Class/Storage/DBI.pm
+++ b/lib/DBIx/Class/Storage/DBI.pm
@@ -1143,8 +1143,10 @@ sub _per_row_update_delete {
 
   my $guard = $self->txn_scope_guard;
 
-  my $subrs_cur = $rs->cursor;
+  # emulate the return value of $sth->execute for non-selects
   my $row_cnt = '0E0';
+
+  my $subrs_cur = $rs->cursor;
   while (my @pks = $subrs_cur->next) {
 
     my $cond;
diff --git a/lib/DBIx/Class/Storage/DBI/mysql.pm b/lib/DBIx/Class/Storage/DBI/mysql.pm
index 7391593..dcdeafe 100644
--- a/lib/DBIx/Class/Storage/DBI/mysql.pm
+++ b/lib/DBIx/Class/Storage/DBI/mysql.pm
@@ -52,7 +52,7 @@ sub lag_behind_master {
 }
 
 # MySql can not do subquery update/deletes, only way is slow per-row operations.
-# This assumes you have proper privilege separation and use innodb.
+# This assumes you have set proper transaction isolation and use innodb.
 sub subq_update_delete {
   return shift->_per_row_update_delete (@_);
 }