Standards Compliance

SQL/ODBC

The compliance level of SQL/ODBC for Reality is:

• ODBC version 2.5.
• Applications Programming Interface (API) Level 2.

• Core language, subject to the exception below.

• The ODBC driver supports the update from one statement of the cursor in another statement. However, the two statements must exist within the same thread in a multi-threaded application. A cursor identifies a current row in a selection statement.

SQL/JDBC

The compliance level of SQL/JDBC for Reality is:

• Java? 2 SDK Standard Edition V1.2.2.
• JDBC 2.0 Core Applications Programming Interface (API).

• JDBC SQL-92 Entry Level Extensions are supported.

  JDBC defines two kinds of extensions to SQL-92 Entry Level that must be supported by a JDBC Compliant driver:

  • Selective Transitional Level syntax and semantics. Currently the only feature at this level that is required for JDBC compliance is the command DROP TABLE.
  • An escape syntax that supports the Selective Transitional Level semantics. A driver should scan for and translate this escape syntax into DBMS-specific syntax. These need only be supported when the underlying database supports the corresponding Transitional Level semantics. Where appropriate, an escape syntax must be included for stored procedures, time and date literals, scalar functions, LIKE escape characters, and outer joins.

  JDBC supports the same DBMS-independent escape syntax as ODBC. By mapping this escape syntax into DBMS-specific syntax, a driver allows portability of application programs that require these features.

  It should be noted, however, that the Reality JDBC Driver does not claim to be JDBC compliant, because Reality does not fully comply with SQL-92 Entry Level. The driver provides those interfaces and methods supported by Reality — exceptions are thrown by unsupported methods.

Other features of the Reality JDBC Driver are:

• Multithreading - the driver is thread safe.

• Transactions - the following transaction isolation levels are supported:

  • TRANSACTION_READ_UNCOMMITTED
  • TRANSACTION_READ_COMMITTED
  • TRANSACTION_REPEATABLE_READ

• Security:

  Applets The standard Java security manager will prevent an applet from making illegal connections with the driver.

  Network User passwords are encrypted prior to transmission over a network.

• Error Reporting - if a critical error occurs the driver will throw an SQLException, which will provide details on type of error encountered. For non-critical errors the driver will cache an SQLWarning(s) message, these can be retrieved at a later by the client, but this must be done prior to executing a new statement. If Data Truncation occurs during a database read the driver will cache a DataTruncation exception, which is a sub-class of SQLWarning.

Data Types

Java equivalents for the SQL data types supported by Reality are listed below.

SQL Type	Java Type
BIGINT	Long
BIT	Boolean
CHAR	String
DATE	java.sql.Date
DECIMAL	java.math.BigDecimal
DOUBLE	Double
FLOAT	Double
INTEGER	Int
LONGVARCHAR	String
NUMERIC	java.math.BigDecimal
REAL	Float
SMALLINT	Short
TIME	java.sql.Time
TIMESTAMP	java.sql.Timestamp
TINYINT	Byte
VARCHAR	String