summaryrefslogtreecommitdiff
path: root/sql/sql_class.h
diff options
context:
space:
mode:
authorkonstantin@mysql.com <>2004-01-19 23:34:40 +0300
committerkonstantin@mysql.com <>2004-01-19 23:34:40 +0300
commiteb0ae211c589ca767a464b47da2fda98fabce674 (patch)
tree6d948ffd777d8eaf819e0fe88bc6919c3bb47372 /sql/sql_class.h
parentc74cd37cd1c0e3334aa30c2a8e45aec9cf482bba (diff)
downloadmariadb-git-eb0ae211c589ca767a464b47da2fda98fabce674.tar.gz
more clear (grammar mistake)
Diffstat (limited to 'sql/sql_class.h')
-rw-r--r--sql/sql_class.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/sql/sql_class.h b/sql/sql_class.h
index 4bdf5c38a2c..7971137d848 100644
--- a/sql/sql_class.h
+++ b/sql/sql_class.h
@@ -627,13 +627,13 @@ public:
/*
During a MySQL session, one can lock tables in two modes: automatic
or manual. In automatic mode all necessary tables are locked just before
- statement execution, and all acquired locks are stored in a 'lock'
+ statement execution, and all acquired locks are stored in 'lock'
member. Unlocking takes place automatically as well, when the
statement ends.
Manual mode comes into play when a user issues a 'LOCK TABLES'
statement. In this mode the user can only use the locked tables.
Trying to use any other tables will give an error. The locked tables are
- stored in a 'locked_tables' member. Manual locking is described in
+ stored in 'locked_tables' member. Manual locking is described in
the 'LOCK_TABLES' chapter of the MySQL manual.
See also lock_tables() for details.
*/