Conventions Used in This Book
The following conventions are used in this book:
- Italic
Used for URLs and for emphasis when introducing a new term.
Constant widthUsed for MySQL and SQL keywords and for code examples.
Constant width boldIn some code examples, highlights the statements being discussed.
Constant width italicIn some code examples, indicates an element (e.g., a filename) that you supply.
- UPPERCASE
In code examples, generally indicates MySQL keywords.
- lowercase
In code examples, generally indicates user-defined items such as variables, parameters, etc.
- punctuation
In code examples, enter exactly as shown.
- indentation
In code examples, helps to show structure but is not required.
—In code examples, begins a single-line comment that extends to the end of a line.
/*and*/In code examples, delimit a multiline comment that can extend from one line to another.
.In code examples and related discussions, qualifies a reference by separating an object name from a component name.
[ ]In syntax descriptions, enclose optional items.
{ }In syntax descriptions, enclose a set of items from which you must choose only one.
|In syntax descriptions, separates the items enclosed in curly brackets, as in {TRUE | FALSE}.
...In syntax descriptions, indicates repeating elements. An ellipsis also shows that statements or clauses irrelevant to the discussion were left out.
Tip
Indicates a tip, suggestion, or general note. For example, we'll tell you if a certain setting is version-specific.
Warning
Indicates a warning or ...