diff options
author | konstantin@oak.local <> | 2004-01-19 23:34:39 +0300 |
---|---|---|
committer | konstantin@oak.local <> | 2004-01-19 23:34:39 +0300 |
commit | c74cd37cd1c0e3334aa30c2a8e45aec9cf482bba (patch) | |
tree | 73a008e7bb19da76e4b2464c7107235f9fbd41e4 /sql/sql_class.h | |
parent | 6b94ea53d58cef981dcdb32fc3887ca0816a46fc (diff) | |
download | mariadb-git-c74cd37cd1c0e3334aa30c2a8e45aec9cf482bba.tar.gz |
More comments to THD::lock and THD::locked_tables commented
Diffstat (limited to 'sql/sql_class.h')
-rw-r--r-- | sql/sql_class.h | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/sql/sql_class.h b/sql/sql_class.h index 5390e8a4ac4..4bdf5c38a2c 100644 --- a/sql/sql_class.h +++ b/sql/sql_class.h @@ -624,6 +624,19 @@ public: and are still in use by this thread */ TABLE *open_tables,*temporary_tables, *handler_tables, *derived_tables; + /* + 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' + 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 + the 'LOCK_TABLES' chapter of the MySQL manual. + See also lock_tables() for details. + */ MYSQL_LOCK *lock; /* Current locks */ MYSQL_LOCK *locked_tables; /* Tables locked with LOCK */ /* |