driver

Type Members

1. trait DerbyDriver extends JdbcDriver

   

   Slick driver for Derby/JavaDB.

   Slick driver for Derby/JavaDB.

   This driver implements slick.driver.JdbcProfile without the following capabilities:

   • slick.profile.RelationalProfile.capabilities.functionDatabase: Functions.database is not available in Derby. Slick will return an empty string instead.
   • slick.profile.RelationalProfile.capabilities.replace, slick.profile.RelationalProfile.capabilities.reverse: These String functions are not available in Derby.
   • slick.profile.RelationalProfile.capabilities.pagingNested: See DERBY-5911.
   • slick.driver.JdbcProfile.capabilities.returnInsertOther: When returning columns from an INSERT operation, only a single column may be specified which must be the table's AutoInc column.
   • slick.profile.SqlProfile.capabilities.sequenceCurr: Sequence.curr to get the current value of a sequence is not supported by Derby. Trying to generate SQL code which uses this feature throws a SlickException.
   • slick.profile.SqlProfile.capabilities.sequenceCycle: Sequence cycling is supported but does not conform to SQL:2008 semantics. Derby cycles back to the START value instead of MINVALUE or MAXVALUE.
   • slick.profile.RelationalProfile.capabilities.zip: Ordered sub-queries and window functions with orderings are currently not supported by Derby. These are required by zip and zipWithIndex. Trying to generate SQL code which uses this feature causes the DB to throw an exception. We do not prevent these queries from being generated because we expect future Derby versions to support them with the standard SQL:2003 syntax (see http://wiki.apache.org/db-derby/OLAPRowNumber).
   • slick.profile.RelationalProfile.capabilities.joinFull: Full outer joins are emulated because there is not native support for them.
   • slick.driver.JdbcProfile.capabilities.insertOrUpdate: InsertOrUpdate operations are emulated on the client side because there is no native support for them (but there is work in progress: see DERBY-3155).
   • slick.driver.JdbcProfile.capabilities.booleanMetaData: Derby <= 10.6 doesn't have booleans, so Slick maps to SMALLINT instead. Other jdbc drivers like MySQL map TINYINT(1) back to a Scala Boolean. Derby maps SMALLINT to an Integer and that's how it shows up in the jdbc meta data, thus the original type is lost.
   • slick.driver.JdbcProfile.capabilities.supportsByte: Derby doesn't have a corresponding type for Byte. SMALLINT is used instead and mapped to Short in the Slick model.
   • slick.profile.RelationalProfile.capabilities.repeat: There's not builtin string function repeat in Derby. https://db.apache.org/derby/docs/10.10/ref/rrefsqlj29026.html

2. trait H2Driver extends JdbcDriver

   

   Slick driver for H2.

   Slick driver for H2.

   This driver implements slick.driver.JdbcProfile without the following capabilities:

   • slick.profile.RelationalProfile.capabilities.reverse: This String function is not available in H2.
   • slick.profile.SqlProfile.capabilities.sequenceMin, slick.profile.SqlProfile.capabilities.sequenceMax, slick.profile.SqlProfile.capabilities.sequenceCycle: H2 does not support MINVALUE, MAXVALUE and CYCLE
   • slick.driver.JdbcProfile.capabilities.returnInsertOther: When returning columns from an INSERT operation, only a single column may be specified which must be the table's AutoInc column.
   • slick.profile.RelationalProfile.capabilities.joinFull: Full outer joins are emulated because there is not native support for them.
   • slick.driver.JdbcProfile.capabilities.insertOrUpdate: InsertOrUpdate operations are emulated on the client side if the data to insert contains an AutoInc fields. Otherwise the operation is performmed natively on the server side.

3. trait HsqldbDriver extends JdbcDriver

   

   Slick driver for HyperSQL (starting with version 2.0).

   Slick driver for HyperSQL (starting with version 2.0).

   This driver implements the slick.driver.JdbcProfile without the following capabilities:

   • slick.profile.SqlProfile.capabilities.sequenceCurr: Sequence.curr to get the current value of a sequence is not supported by Hsqldb. Trying to generate SQL code which uses this feature throws a SlickException.
   • 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.

4. class InsertBuilderResult extends AnyRef

   

5. trait JdbcActionComponent extends SqlActionComponent

   

6. trait JdbcDriver extends SqlDriver with JdbcProfile with JdbcStatementBuilderComponent with JdbcMappingCompilerComponent

   

   The internal implementation details of JdbcProfile-based drivers.

   The internal implementation details of JdbcProfile-based drivers. These can be used by driver implementors but are not intended to be accessed by users of a driver.

7. trait JdbcExecutorComponent extends SqlExecutorComponent

   

   The part of the driver cake that handles the executor API for running queries.

   The part of the driver cake that handles the executor API for running queries.

8. trait JdbcInsertInvokerComponent extends BasicInsertInvokerComponent

   

   A slice of the JdbcProfile cake which provides the functionality for different kinds of insert operations.

9. trait JdbcInvokerComponent extends BasicInvokerComponent

   

10. trait JdbcModelComponent extends AnyRef

    

11. trait JdbcProfile extends SqlProfile with JdbcActionComponent with JdbcInvokerComponent with JdbcInsertInvokerComponent with JdbcExecutorComponent with JdbcTypesComponent with JdbcModelComponent

    

    A profile for accessing SQL databases via JDBC.

    A profile for accessing SQL databases via JDBC. All drivers for JDBC-based databases implement this profile.

12. trait JdbcStatementBuilderComponent extends AnyRef

    

13. trait JdbcTypesComponent extends RelationalTypesComponent

    

14. trait MySQLDriver extends JdbcDriver

    

    Slick driver for MySQL.

    Slick driver for MySQL.

    This driver implements slick.driver.JdbcProfile without the following capabilities:

    • slick.driver.JdbcProfile.capabilities.returnInsertOther: When returning columns from an INSERT operation, only a single column may be specified which must be the table's AutoInc column.
    • slick.profile.SqlProfile.capabilities.sequenceLimited: Non-cyclic sequence may not have an upper limit.
    • slick.profile.RelationalProfile.capabilities.joinFull: Full outer joins are emulated because there is not native support for them.
    • slick.driver.JdbcProfile.capabilities.nullableNoDefault: Nullable columns always have NULL as a default according to the SQL standard. Consequently MySQL treats no specifying a default value just as specifying NULL and reports NULL as the default value. Some other dbms treat queries with no default as NULL default, but distinguish NULL from no default value in the meta data.

    Sequences are supported through an emulation which requires the schema to be created by Slick. You can also use an existing schema with your own sequence emulation if you provide for each sequence s a pair of functions s_nextval and s_currval.

    The default type for strings of unlimited length is "TEXT". This can be changed by overriding slick.driver.MySQL.defaultStringType in application.conf.

15. trait PostgresDriver extends JdbcDriver

    

    Slick driver for PostgreSQL.

    Slick driver for PostgreSQL.

    This driver implements slick.driver.JdbcProfile without the following capabilities:

    • slick.driver.JdbcProfile.capabilities.insertOrUpdate: InsertOrUpdate operations are emulated on the server side with a single JDBC statement executing multiple server-side statements in a transaction. This is faster than a client-side emulation but may still fail due to concurrent updates. InsertOrUpdate operations with returning are emulated on the client side.
    • slick.driver.JdbcProfile.capabilities.nullableNoDefault: Nullable columns always have NULL as a default according to the SQL standard. Consequently Postgres treats no specifying a default value just as specifying NULL and reports NULL as the default value. Some other dbms treat queries with no default as NULL default, but distinguish NULL from no default value in the meta data.
    • slick.driver.JdbcProfile.capabilities.supportsByte: Postgres doesn't have a corresponding type for Byte. SMALLINT is used instead and mapped to Short in the Slick model.

    Notes:

    • slick.profile.RelationalProfile.capabilities.typeBlob: The default implementation of the Blob type uses the database type lo and the stored procedure lo_manage, both of which are provided by the "lo" extension in PostgreSQL.

16. trait SQLiteDriver extends JdbcDriver

    

    Slick driver for SQLite.

    Slick driver for SQLite.

    This driver implements slick.driver.JdbcProfile without the following capabilities:

    • slick.profile.RelationalProfile.capabilities.functionDatabase, slick.profile.RelationalProfile.capabilities.functionUser: Functions.user and Functions.database are not available in SQLite. Slick will return empty strings for both.
    • slick.profile.RelationalProfile.capabilities.joinFull, slick.profile.RelationalProfile.capabilities.joinRight: Right and full outer joins are emulated because there is not native support for them.
    • slick.driver.JdbcProfile.capabilities.mutable: SQLite does not allow mutation of result sets. All cursors are read-only.
    • slick.profile.SqlProfile.capabilities.sequence: Sequences are not supported by SQLite.
    • slick.driver.JdbcProfile.capabilities.returnInsertOther: When returning columns from an INSERT operation, only a single column may be specified which must be the table's AutoInc column.
    • slick.profile.RelationalProfile.capabilities.typeBigDecimal: SQLite does not support a decimal type.
    • slick.profile.RelationalProfile.capabilities.typeBlob: Blobs are not supported by the SQLite JDBC driver (but binary data in the form of Array[Byte] is).
    • slick.profile.RelationalProfile.capabilities.zip: Row numbers (required by zip and zipWithIndex) are not supported. Trying to generate SQL code which uses this feature throws a SlickException.
    • slick.driver.JdbcProfile.capabilities.insertOrUpdate: InsertOrUpdate operations are emulated on the client side if the data to insert contains an AutoInc field. Otherwise the operation is performmed natively on the server side.
    • slick.driver.JdbcProfile.capabilities.defaultValueMetaData: The stable xerial sqlite-jdbc driver 3.7.2 does not return default values for columns in the DatabaseMetaData. Consequently they also do not appear in Slick's model. This has been fixed in sqlite-jdbc, but the only released version that contains the fix is milestone 3.7.15-M1. You can use it instead of the stable 3.7.2 in order to get default values with SQLite. Also see https://code.google.com/p/sqlite-jdbc/issues/detail?id=27
    • slick.driver.JdbcProfile.capabilities.booleanMetaData: SQlite doesn't have booleans, so Slick maps to INTEGER instead. Other jdbc drivers like MySQL map TINYINT(1) back to a Scala Boolean. SQlite maps INTEGER to an Integer and that's how it shows up in the jdbc meta data, thus the original type is lost.
    • slick.driver.JdbcProfile.capabilities.distinguishesIntTypes: SQLite does not distinguish integer types and maps them all to Int in the meta data.
    • slick.driver.JdbcProfile.capabilities.supportsByte: SQLite does not distinguish integer types and maps them all to Int in the meta data.

17. trait AccessDriver extends JdbcDriver

    

    Slick driver for Microsoft Access via JdbcOdbcDriver.

    Slick driver for Microsoft Access via JdbcOdbcDriver.

    This driver implements slick.driver.JdbcProfile without the following capabilities:

    • slick.profile.RelationalProfile.capabilities.columnDefaults: Access does not allow the definition of default values through ODBC but only via OLEDB/ADO. Trying to generate DDL SQL code which uses this feature throws a SlickException.
    • slick.profile.RelationalProfile.capabilities.foreignKeyActions: All foreign key actions are ignored. Access supports CASCADE and SET NULL but not through ODBC, only via OLEDB/ADO.
    • slick.profile.RelationalProfile.capabilities.functionDatabase, slick.profile.RelationalProfile.capabilities.functionUser: Functions.user and Functions.database are not available in Access. Slick will return empty strings for both.
    • slick.profile.RelationalProfile.capabilities.likeEscape: Access does not allow you to specify a custom escape character for like.
    • slick.profile.RelationalProfile.capabilities.pagingDrop: Drop(n) modifiers are not supported. Trying to generate SQL code which uses this feature throws a SlickException.
    • slick.profile.RelationalProfile.capabilities.pagingPreciseTake: Take(n) modifiers are mapped to SELECT TOP n which may return more rows than requested if they are not unique.
    • slick.profile.SqlProfile.capabilities.sequence: Sequences are not supported by Access
    • slick.driver.JdbcProfile.capabilities.returnInsertKey, slick.driver.JdbcProfile.capabilities.returnInsertOther: Returning columns from an INSERT operation is not supported. Trying to execute such an insert statement throws a SlickException.
    • slick.profile.RelationalProfile.capabilities.typeBlob: Trying to use java.sql.Blob objects causes a NPE in the JdbcOdbcDriver. Binary data in the form of Array[Byte] is supported.
    • slick.profile.RelationalProfile.capabilities.setByteArrayNull: Setting an Option[ Array[Byte] ] column to None causes an Exception in the JdbcOdbcDriver.
    • slick.profile.RelationalProfile.capabilities.typeBigDecimal, slick.profile.RelationalProfile.capabilities.typeLong: Access does not support decimal or long integer types.
    • slick.profile.RelationalProfile.capabilities.zip: Row numbers (required by zip and zipWithIndex) are not supported. Trying to generate SQL code which uses this feature throws a SlickException.
    • slick.profile.RelationalProfile.capabilities.joinFull: Full outer joins are emulated because there is not native support for them.
    • slick.driver.JdbcProfile.capabilities.insertOrUpdate: InsertOrUpdate operations are emulated on the client side because there is no native support for them.

    Annotations

    @deprecated

    Deprecated

    (Since version 2.1) AccessDriver will be removed when we drop support for Java versions < 8