This driver implements slick.driver.JdbcProfilewithout the following capabilities:
slick.profile.RelationalProfile.capabilities.foreignKeyActions:
Foreign key actions Cascade, SetNull and NoAction are
directly supported for onDelete. Restrict and SetDefault
are ignored (i.e. equals to NoAction). No onUpdate actions are
supported but specifying Cascade adds the option INITIALLY DEFERRED
to the foreign key constraint, thus allowing you to perform the
cascading update manually before committing the current transaction.
Other onUpdate actions are ignored.
slick.driver.JdbcProfile.capabilities.insertOrUpdate:
InsertOrUpdate operations are emulated on the client side if generated
keys should be returned. Otherwise the operation is performmed
natively on the server side.
slick.driver.JdbcProfile.capabilities.booleanMetaData:
Oracle doesn't have booleans, so Slick maps to CHAR instead and
that's how it appears in model and generated code.
slick.driver.JdbcProfile.capabilities.distinguishesIntTypes:
Oracle doesn't distinguish integer types and Slick uses NUMBER,
which is always mapped back to BigDecimal in model and generated code.
slick.driver.JdbcProfile.capabilities.supportsByte:
Oracle does not have a BYTE type.
Note: The Oracle JDBC driver has problems with quoted identifiers. Columns
which are returned from inserts must not require quoted names (in
particular, they must not contain lower-case characters or be equal to a
reserved word), otherwise a bug in the Oracle JDBC driver triggers an
ORA-00904 error. The same issue arises when trying to update such a column
in a mutable result set.
Updating Blob values in updatable result sets is not supported.
Slick driver for Oracle.
This driver implements
slick.driver.JdbcProfilewithout the following capabilities:slick.profile.RelationalProfile.capabilities.foreignKeyActions: Foreign key actions Cascade, SetNull and NoAction are directly supported for onDelete. Restrict and SetDefault are ignored (i.e. equals to NoAction). No onUpdate actions are supported but specifying Cascade adds the option INITIALLY DEFERRED to the foreign key constraint, thus allowing you to perform the cascading update manually before committing the current transaction. Other onUpdate actions are ignored.Note: The Oracle JDBC driver has problems with quoted identifiers. Columns which are returned from inserts must not require quoted names (in particular, they must not contain lower-case characters or be equal to a reserved word), otherwise a bug in the Oracle JDBC driver triggers an ORA-00904 error. The same issue arises when trying to update such a column in a mutable result set.
Updating Blob values in updatable result sets is not supported.