Mysql 体系结构系列之三

前言：接上一篇Mysql 体系结构系列之二： 核心模块之间的交互

                 Mysql 体系结构系列之二：http://blog.csdn.net/u010993297/article/details/9407115

1. 核心模块之间的交互 Interaction of the Core Modules

<<-------第三段 讲的是连接线程转到命令调度器----->>

The Connection Thread passes the request data to theCommand Dispatcher.

连接线程请求数据传递给命令调度器。

Some requests, known in the MySQL code terminology as commands, can be accommodated by the Command Dispatcherdirectly, while more complex ones need to be redirected to another module.

某些请求，在Mysql代码术语里也被称为“命令”，可以直接被命令调度器接纳，而一些更复杂的请求则被转发给其他模块。

A typical command may request the server to run a query, change the active database, report the status, send a continuous dump of the replication updates, close the connection, or perform some other operation.

一个典型的命令可以请求服务器运行查询、更改主动数据库、报告状态、发送复制更新的连续转储、关闭连接或执行一些其他的操作。

 

<<-------第四段 讲的是解析器----->>

In MySQL server terminology, there are two types of client requests: aquery and a command.

在Mysql服务器的术语中，有两种类型的客户端请求：查询和命令。

A query is anything that has to go through theparser.

查询是任何必须通过解析器的请求。

A command is a request that can be executed without the need to invoke theparser. We will use the term query in the context of MySQL internals.

命令是无需调用解析器即可执行的请求。我们将在Mysql内核结构上下文中使用查询整个术语。

Thus, not only a SELECT but also a DELETE or INSERT in our terminology would be called a query. What we would call a query is sometimes called an SQL statement.

即不仅select在我们的术语中可以称为查询，delete或insert也可以称为查询。我们所说的查询有时也被成为SQL语句。

 

<<-------第五段 讲的是命令调度器到日志记录模块----->>

If full query logging is enabled, theCommand Dispatcher will ask the Logging Module

to log the query or the command to the plain-text log prior to the dispatch.

如果启用了全查询日志记录，命令调度器将在调度前要求日志记录模块将查询或命令记录在纯文本日志中。

Thus in the full logging configuration all queries will be logged, even the ones that are not syntactically correct and will never be executed, immediately returning an error.

因此，全日志记录配置中，所以的查询都将被记录，即使是由于语法错误而绝不会执行并立即返回一个错误的查询也不例外。

 

今天先看这三个小段，明日继续更新中。。。