Overview of Oracle Extensions to the SQLJ Standard

The Oracle SQLJ translator accepts a broader range of SQL syntax than the ANSI SQLJ Standard specifies.

The standard addresses only the SQL92 dialect of SQL, but allows extension beyond that. Oracle SQLJ supports Oracle's SQL dialect, which is a superset of SQL92. Therefore, if you must create SQLJ programs that work with other DBMS vendors, you should avoid using SQL syntax and SQL types that are not in the standard and therefore might not be supported in other environments.

Oracle SQLJ supports the following Java types as extensions to the SQLJ standard. Do not use these or other types if you may want to use your code in other environments. To ensure that your application is portable, use the Oracle SQLJ -warn=portable flag. (See "Translator Warnings (-warn)".)

• instances of oracle.sql.* classes as wrappers for SQL data (see "Oracle Type Extensions")

• custom Java classes (classes that implement the CustomDatum interface), typically produced by the Oracle JPublisher utility, to correspond to SQL objects, object references, and collections (see "About Custom Java Classes and the CustomDatum Interface")

• stream instances (AsciiStream, BinaryStream, UnicodeStream) used as output parameters (see "Support for Streams")

• iterator and result set instances as input or output parameters anywhere (the standard specifies them only in result expressions or cast statements; see "Using Iterators and Result Sets as Host Variables" and "Using Iterators and Result Sets as Stored Function Returns")

For information about the oracle.sql package, see "Oracle Type Extensions".

For general information about Oracle SQLJ extensions, see Chapter 5, "Type Support", and Chapter 6, "Objects and Collections".

---