Conventions Used in This Book
The following conventions are used in this book: Italic
Used for filenames, directory names, URLs, and occasional emphasis.
Constant width
Used for code examples, and used in text for table names, view names,
and other user-defined names of database objects.
Constant width bold
Used in examples that show interaction between SQL*Plus and a user.
Commands typed by the user are shown in bold, but output from
SQL*Plus is shown in normal text.
Constant width italic
In some code examples, and in many syntax diagrams, indicates an
element (e.g., a filename) you supply.
UPPERCASE
Generally indicates SQL and SQL*Plus keywords.
lowercase
In code examples, generally indicates user-defined items such as
variables, parameters, etc.
In code examples, a double hyphen begins a single-line comment, which
extends to the end of a line.
/* and */
In code examples, these characters delimit a multiline comment, which
can extend from one line to another.
.
In code examples and related discussions, a dot qualifies a reference
by separating an object name from a component name. In this book, dot
notation is most often used in fully qualified column names, which
you will see written as
table_name.column_name.
The dot separates the table name from the column name.
[ ]
In syntax descriptions, square brackets enclose optional items.
{ }
In syntax descriptions, curly brackets enclose a set of items from
which you must choose only one.
|
In syntax descriptions, a vertical bar separates the items enclosed
in square or curly brackets, as in {VARCHAR2 | DATE | NUMBER}.
::=
In syntax descriptions, indicates an expansion of a syntax element.
|
Indicates a tip, suggestion, or general note. For example,
I'll tell you if you need to use a particular
SQL*Plus version, or if an operation requires certain privileges. |
|
|
Indicates a warning or caution. For example, I'll
tell you if SQL*Plus does not behave as you'd
expect, or if a particular operation has a negative impact on
performance. |
|
|