mysql官方文档阅读笔记(三)General Information一般信息模块浏览

在网上找了找，很多大神都在研究mysql数据库源码，还是值得一看啊。但我还是老老实实的看文档。后面再深入研究。现在来研究General Information下的东西。翻译很苦逼，当初该多学学英语啊。不过现在还不是太晚。这样看了试着翻译，不会再用百度。慢慢还是可以提高的。还是挺有成就感的。

  

1.1 About This Manual-------------------------------------------------------------------------------------------------------关于本手册 1.2 Typographical and Syntax Conventions-------------------------------------------------------------------------拼写和语法约定 1.3 Overview of the MySQL Database Management System------------------------------------------------ MySQL数据库管理系统综述     1.4 What Is New in MySQL 5.7-----------------------------------------------------------------------------------------什么是新的MySQL 5.7 1.5 Server and Status Variables and Options Added, Deprecated, or Removed in MySQL 5.7-服务器和状态变量和选择的，过时的，或在MySQL 5.7删除 1.6 MySQL Information Sources-----------------------------------------------------------------------------------------MySQL的信息来源      1.7 How to Report Bugs or Problems----------------------------------------------------------------------------------如何报告错误或问题 1.8 MySQL Standards Compliance-------------------------------------------------------------------------------------MySQL的标准      1.9 Credits-----------------------------------------------------------------------------------------------------------------------信用(这里讲了如何投稿，哪些开发者做了贡献等)   1.1好的，现在我们来细化一级 ：

1.1 About This Manual

This is the Reference Manual for the MySQL Database System, version 5.7, through release 5.7.19. Differences between minor versions of MySQL 5.7 are noted in the present text with reference to release numbers (5.7.x).

This manual is not intended for use with older versions of the MySQL software due to the many functional and other differences between MySQL 5.7 and previous versions. If you are using an earlier release of the MySQL software, please refer to the appropriate manual. For example, MySQL 5.6 Reference Manual covers the 5.6 series of MySQL software releases.

Because this manual serves as a reference, it does not provide general instruction on SQL or relational database concepts. It also does not teach you how to use your operating system or command-line interpreter.

The MySQL Database Software is under constant development, and the Reference Manual is updated frequently as well. The most recent version of the manual is available online in searchable form at http://dev.mysql.com/doc/. Other formats also are available there, including HTML, PDF, and EPUB versions.

The Reference Manual source files are written in DocBook XML format. The HTML version and other formats are produced automatically, primarily using the DocBook XSL stylesheets. For information about DocBook, see http://docbook.org/

If you have questions about using MySQL, you can ask them using our mailing lists or forums. See Section 1.6.1, “MySQL Mailing Lists”, and Section 1.6.2, “MySQL Community Support at the MySQL Forums”. If you have suggestions concerning additions or corrections to the manual itself, please send them to the http://www.mysql.com/company/contact/.

This manual was originally written by David Axmark and Michael “Monty” Widenius. It is maintained by the MySQL Documentation Team, consisting of Chris Cole, Paul DuBois, Edward Gilmore, Stefan Hinz, David Moss, Philip Olson, Daniel Price, Daniel So, and Jon Stephens.

 PREV    HOME    UP    NEXT 

 User Comments

Sign Up LoginYou must be logged in to post a comment.

这是MySQL数据库系统，参考手册5.7版，通过释放5.7.19。MySQL 5.7的次要版本之间的差异，在本文本中提到的版本号（5.7 x）。

本手册不打算使用与MySQL软件的旧版本，由于MySQL 5.7和以前的版本之间的许多功能和其他差异。如果您使用的是MySQL软件的早期版本，请参阅相应的手册。例如，MySQL 5.6参考手册涵盖了MySQL软件发布的5.6个系列。

因为本手册作为参考，它不提供SQL或关系数据库概念的一般说明。它也不会教你如何使用你的操作系统或命令行解释器。

MySQL数据库软件正在不断开发中，参考手册也经常更新。本手册的最新版本是在网上搜索HTTP：/ / dev.mysql形式。COM /医生/。也有其他格式，包括HTML，PDF，EPUB版本。

参考手册源文件是用DocBook XML格式。HTML版本和其他格式的自动生成，主要使用DocBook XSL样式表。关于DocBook，看到http://docbook.org/

如果你有关于使用MySQL的问题，你可以问他们使用我们的邮件列表或论坛。见第1.6.1，MySQL邮件列表”，与第1.6.2，MySQL社区支持MySQL论坛”。如果你有关于补充或者改正的手册本身的建议，请发送给HTTP：/ / www.mysql。COM /公司/接触/。

本手册最初是由David Axmark写的，米迦勒“Monty Widenius”。它是由MySQL文档团队维护，包括Chris Cole，Paul DuBois，Edward Gilmore，Stefan Hinz，David Moss，Philip Olson，Daniel Price，Daniel So，Jon Stephens。

PREV -----------------------------------------------------------------上期

User Comments---------------------------------------------------用户评论

You must be logged in to post a comment.--------------您必须登录才能发表评论。

1.2吃了晚饭我们来第二小结吧。

1.2 Typographical and Syntax Conventions

This manual uses certain typographical conventions:

• Text in this style is used for SQL statements; database, table, and column names; program listings and source code; and environment variables. Example: “To reload the grant tables, use the FLUSH PRIVILEGES statement.”

• Text in this style indicates input that you type in examples.

• Text in this style indicates the names of executable programs and scripts, examples being mysql (the MySQL command-line client program) andmysqld (the MySQL server executable).

• Text in this style is used for variable input for which you should substitute a value of your own choosing.

• Text in this style is used for emphasis.

• Text in this style is used in table headings and to convey especially strong emphasis.

• Text in this style is used to indicate a program option that affects how the program is executed, or that supplies information that is needed for the program to function in a certain way. Example: “The --host option (short form -h) tells the mysql client program the hostname or IP address of the MySQL server that it should connect to”.

• File names and directory names are written like this: “The global my.cnf file is located in the /etc directory.”

• Character sequences are written like this: “To specify a wildcard, use the ‘%’ character.”

When commands are shown that are meant to be executed from within a particular program, the prompt shown preceding the command indicates which command to use. For example, shell> indicates a command that you execute from your login shell, root-shell> is similar but should be executed asroot, and mysql> indicates a statement that you execute from the mysql client program:

shell> type a shell command here
root-shell> type a shell command as root here
mysql> type a mysql statement here

In some areas different systems may be distinguished from each other to show that commands should be executed in two different environments. For example, while working with replication the commands might be prefixed with master and slave:

master> type a mysql command on the replication master here
slave> type a mysql command on the replication slave here

The “shell” is your command interpreter. On Unix, this is typically a program such as sh, csh, or bash. On Windows, the equivalent program iscommand.com or cmd.exe, typically run in a console window.

When you enter a command or statement shown in an example, do not type the prompt shown in the example.

Database, table, and column names must often be substituted into statements. To indicate that such substitution is necessary, this manual uses db_name,tbl_name, and col_name. For example, you might see a statement like this:

mysql> SELECT col_name FROM db_name.tbl_name;

This means that if you were to enter a similar statement, you would supply your own database, table, and column names, perhaps like this:

mysql> SELECT author_name FROM biblio_db.author_list;

SQL keywords are not case sensitive and may be written in any lettercase. This manual uses uppercase.

In syntax descriptions, square brackets (“[” and “]”) indicate optional words or clauses. For example, in the following statement, IF EXISTS is optional:

DROP TABLE [IF EXISTS] tbl_name

When a syntax element consists of a number of alternatives, the alternatives are separated by vertical bars (“|”). When one member from a set of choicesmay be chosen, the alternatives are listed within square brackets (“[” and “]”):

TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)

When one member from a set of choices must be chosen, the alternatives are listed within braces (“{” and “}”):

{DESCRIBE | DESC} tbl_name [col_name | wild]

An ellipsis (...) indicates the omission of a section of a statement, typically to provide a shorter version of more complex syntax. For example, SELECT ... INTO OUTFILE is shorthand for the form of SELECT statement that has an INTO OUTFILE clause following other parts of the statement.

An ellipsis can also indicate that the preceding syntax element of a statement may be repeated. In the following example, multiple reset_option values may be given, with each of those after the first preceded by commas:

RESET reset_option [,reset_option] ...

Commands for setting shell variables are shown using Bourne shell syntax. For example, the sequence to set the CC environment variable and run theconfigure command looks like this in Bourne shell syntax:

shell> CC=gcc ./configure

If you are using csh or tcsh, you must issue commands somewhat differently:

    

     

      
     
    
shell> setenv CC gcc
shell> ./configure

本手册使用一定的排版约定：


-此样式的文本用于SQL语句；数据库、表和列名称；程序清单和源代码；以及环境变量。例如：“重新加载授予表，使用刷新特权语句。”

-这种样式的文本指示输入的输入实例。

-在这种风格的文本表示的可执行程序和脚本的名称、实例MySQL（MySQL的命令行客户端程序）andmysqld（MySQL服务器可执行）。

-此样式的文本用于变量输入，您应该用您自己选择的值替换。

-这种风格的文本用于强调。

-此样式的文本用于表标题，并传达特别强的强调。

-此样式的文本用于指示影响程序执行的程序选项，或提供程序需要以某种方式运行的信息。例如：“宿主选项（简称H）告诉MySQL客户端程序的主机名或IP地址的MySQL服务器，它应该连接到”。

-文件名和目录名是这样写的：“全球my.cnf文件位于/etc目录。”

-字符序列是这样写的：“要指定通配符，请使用“%”字符。

当显示要从特定程序执行的命令时，命令前面显示的提示指示要使用哪个命令。例如，壳>表示一个命令，你执行你的登录shell，根壳>相似，但应该被处决了，和MySQL >表示一个声明，你执行从MySQL客户端程序：

shell>在这里键入shell命令

root-shell>在这里键入一个root权限的shell命令

mysql> 在这里键入一个MySQL语句

在某些地区，不同的系统可以彼此区分，以显示命令应该在两个不同的环境中执行。例如，在复制的命令可能以主从工作：

master>在主重复制主机里面键入一个命令

slave>在主重复制被控机里面键入一个命令

“shell”是你的命令解释器。在Unix上，这是一个典型的程序如sh或bash、csh、。在Windows中，相当于程序iscommand.com或cmd.exe，在控制台窗口通常运行。

输入示例中显示的命令或语句时，不要键入示例中显示的提示。

数据库、表和列名必须经常被替换成语句。表明，这种替代是必要的，本手册使用db_name，tbl_name，和col_name。例如，您可能会看到这样的语句：

mysql> SELECT col_name FROM db_name.tbl_name;

这意味着，如果你要输入一个类似的语句，你将提供你自己的数据库，表和列的名字，也许像这样：

mysql> SELECT author_name FROM biblio_db.author_list;

SQL关键字不区分大小写，可以写在任何lettercase。本手册使用大写字母。
在语法描述中，方括号（“和”）表示可选的词或子句。例如，在下面的语句中，如果存在是可选的：

DROP TABLE [IF EXISTS] tbl_name

当一个语法元素组成的一个替代品，替代品是由竖线隔开（“|”）。当选择一组成员时，备选方案列在方括号内（“和”）：

TRIM([[BOTH | LEADING | TRAILING] [remstr] FROM] str)

当一组成员必须选择一组选择时，备选方案列在括号内（“{”和“}”）中：

{DESCRIBE | DESC} tbl_name [col_name | wild]

省略号（…）表示省略语句的一部分，通常是提供较短的更复杂语法的版本。例如，选择…为导出的文件是速记的形式，有一个SELECT语句到输出文件的以下条款声明的其他部分。

省略号还可以表示语句的前一个语法元素可以重复。在下面的例子中，多reset_option值可能是给定的，每个人在第一前面的逗号：

RESET reset_option [,reset_option] ...

设置shell变量命令显示使用Bourne shell的语法。例如，序列设置CC环境变量和运行配置命令看起来像这样在Bourne shell的语法：

shell> CC=gcc ./configure

如果你正在使用csh或者，你必须发出命令有所不同：

shell> setenv CC gcc
shell> ./configure

先写到这里了。这些貌似还挺可以的。我去吃午饭了。下一节直接找点用处大的看。有的放矢。