Flylib.com

Books Software

 
 
 

Conventions Used in This Book

     

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.


     

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product's documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: " Oracle SQL*Plus: The Definitive Guide , Second Edition, by Jonathan Gennick. Copyright 2005 O'Reilly Media, Inc., 0-596-00746-9."

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.

     

Comments and Questions

Please address comments and questions concerning this book to the publisher:

O'Reilly Media, Inc.
1005 Gravenstein Highway North
Sebastopol, CA 95472
(800) 998-9938 (in the United States or Canada)
(707) 829-0515 (international or local)
(707) 829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:

http://www.oreilly.com/catalog/orsqlplus2

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about our books, conferences, Resource Centers, and the O'Reilly Network, see our web site at:

http://www.oreilly.com