Oracle9i SQLJ Developer's Guide and Reference
Release 1 (9.0.1)

Part Number A90212-01
Go To Documentation Library
Go To Product List
Solution Area
Go To Table Of Contents
Go To Index

Go to previous page Go to next page


This preface introduces you to the Oracle9i SQLJ Developer's Guide and Reference, discussing the intended audience, structure, and conventions of this document. A list of related Oracle documents is also provided.

Intended Audience

This manual is intended for anyone with an interest in SQLJ programming but assumes at least some prior knowledge of the following:

Although general knowledge of SQL and JDBC is sufficient, any knowledge of Oracle-specific SQL and JDBC features would be helpful as well.

See "Related Documents" below for the names of Oracle documents that discuss SQL and JDBC.


The two major aspects of using SQLJ are:

Chapters 3 through 7 provide information about programming features, with chapters 3 and 4 covering the most important aspects.

Chapter 8 provides information about translator options and features.

In all, this document consists of the following chapters and appendixes:

Related Documents

This section lists other documentation of interest.

See the following additional documents available from the Oracle Java Platform group:

You can also refer to the following documents from the Oracle Server Technologies group.

Documentation from the following Oracle groups may also be of interest.

For documentation of SQLJ standard features and syntax, refer to ANSI specification X3.135.10-1998:

You can obtain this from ANSI through the following Web site:

(Click on "Electronic Standards Store" and search for the above specification number.)


This document uses UNIX syntax for file paths (for example: /myroot/myfile.html). If you are using some other kind of operating system, then substitute the appropriate syntax.

This document uses [Oracle Home] to indicate your Oracle home directory.

In addition, this document uses the following conventions:

Convention  Meaning 

italicized regular text 

Italicized regular text is used for emphasis or to indicate a term that is being defined or will be defined shortly. 

. . .  

Horizontal ellipsis points in sample code indicate the omission of a statement or statements or part of a statement. This is done when you would normally expect additional statements or code to appear, but such statements or code would not be related to the example. 

code text 

Code text within regular text indicates class names, object names, method names, variable names, Java types, Oracle datatypes, file names, and directory names. 


Italicized code text in a program statement indicates something that must be provided by the user. 

<italicized_code_text >  

Angle brackets enclosing italicized code text in a program statement indicates something that can optionally be provided by the user. 

In this document, it was not feasible to use more standard conventions, such as square brackets [] to enclose optional items to be provided, because of the particulars of SQLJ coding syntax.

For example, in the following statement the square brackets and curly brackets are part of SQLJ coding syntax, but the angle brackets indicate that connctxt_exp, execctxt_exp, and results_exp are optional entries. You must provide a SQL operation, however.

#sql <[<connctxt_exp><,><execctxt_exp>]> <results_exp> = { SQL operation };

And in the following SQLJ command line option (-user), the angle brackets indicate that conn_context_class and the password (with preceding slash) are optional entries. You must provide a username, however.


Documentation Accessibility

Oracle's goal is to make our products, services, and supporting documentation accessible to the disabled community with good usability. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at:

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Go to previous page Go to next page
Copyright © 1996-2001, Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Go To Product List
Solution Area
Go To Table Of Contents
Go To Index