diff options
| author | unknown <konstantin@mysql.com> | 2004-01-19 23:34:40 +0300 |
|---|---|---|
| committer | unknown <konstantin@mysql.com> | 2004-01-19 23:34:40 +0300 |
| commit | b89abbf8a154376678a3ed8a9fe6ea25b5209aba (patch) | |
| tree | 6d948ffd777d8eaf819e0fe88bc6919c3bb47372 | |
| parent | eead0c1b822070aebdaede48930249aea610fc98 (diff) | |
| download | mariadb-git-b89abbf8a154376678a3ed8a9fe6ea25b5209aba.tar.gz | |
more clear (grammar mistake)
| -rw-r--r-- | sql/sql_class.h | 4 |
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. */ |