From d3f8bf365e5b93f58497a25e07fde7ce30884f9d Mon Sep 17 00:00:00 2001
From: "mkanat%kerio.com" <>
Date: Fri, 18 Feb 2005 05:57:26 +0000
Subject: Bug 280503: Replace "LOCK/UNLOCK TABLES" with Bugzilla::DB function
 call Patch By Tomas Kopal <Tomas.Kopal@altap.cz> r=mkanat,a=myk

---
 userprefs.cgi | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'userprefs.cgi')

diff --git a/userprefs.cgi b/userprefs.cgi
index f62f02500..193a4d73f 100755
--- a/userprefs.cgi
+++ b/userprefs.cgi
@@ -195,7 +195,8 @@ sub DoEmail {
 sub SaveEmail {
     my $updateString = "";
     my $cgi = Bugzilla->cgi;
-    
+    my $dbh = Bugzilla->dbh;
+
     if (defined $cgi->param('ExcludeSelf')) {
         $updateString .= 'ExcludeSelf~on';
     } else {
@@ -226,7 +227,7 @@ sub SaveEmail {
         # we don't really care if anyone reads the watch table.  So 
         # some small amount of contention could be gotten rid of by
         # using user-defined locks rather than table locking.
-        SendSQL("LOCK TABLES watch WRITE, profiles READ");
+        $dbh->bz_lock_tables('watch WRITE', 'profiles READ');
 
         # what the db looks like now
         my $origWatchedUsers = new Bugzilla::RelationSet;
@@ -244,7 +245,7 @@ sub SaveEmail {
         ($CCDELTAS[0] eq "") || SendSQL($CCDELTAS[0]);
         ($CCDELTAS[1] eq "") || SendSQL($CCDELTAS[1]);
 
-        SendSQL("UNLOCK TABLES");       
+        $dbh->bz_unlock_tables();
     }
 }
 
-- 
cgit v1.2.3-24-g4f1b