The back-end type required by this profile
The back-end type required by this profile
Builder for SELECT statements that can be used to check for the existing of primary keys supplied to an INSERT operation.
Builder for column specifications in DDL statements.
The type of a (partially) compiled AST for Insert operations.
The type of a (partially) compiled AST for Insert operations. Unlike querying or deleting, inserts may require different compilation results which should be computed lazily.
An InsertInvoker that returns the number of affected rows.
Pseudo-invoker for running DDL statements.
Pseudo-invoker for running DELETE calls.
An InsertInvoker that can also insert from another query.
Builder for INSERT statements.
The type of insert invokers returned by the driver
The type of insert invokers returned by the driver
The JDBC-specific InsertInvoker with additional methods
An InsertInvoker that returns a mapping of inserted values and generated keys.
Code generator phase for queries on JdbcProfile-based drivers.
Code generator phase for inserts on JdbcProfile-based drivers.
A ResultConverterCompiler that builds JDBC-based converters.
Build a Slick model from introspecting the jdbc meta data.
QueryBuilder mix-in for Oracle-style ROWNUM (applied before ORDER BY and GROUP BY) instead of the standard SQL ROWNUMBER().
Builder for SELECT and UPDATE statements.
The type of query executors returned by the driver
The type of query executors returned by the driver
Base class for QueryExecutor implementations
An Invoker for queries.
In InsertInvoker that returns generated keys or other columns.
QueryBuilder mix-in for pagination based on RowNumber.
The type of a schema description (DDL)
The type of a schema description (DDL)
A schema description contains the SQL statements for creating and dropping database entities.
Builder for DDL statements for sequences.
Builder for various DDL statements.
Builder for UPDATE statements used as part of an insertOrUpdate operation on databases that don't support this in a single server-side statement.
Pseudo-invoker for running UPDATE calls.
Builder for upsert statements, builds standard SQL MERGE statements by default.
The back-end implementation for this profile
The back-end implementation for this profile
The capabilities supported by this driver.
The capabilities supported by this driver. This can be used to query at runtime whether a specific feature is supported.
(Partially) ompile an AST for insert operations
(Partially) ompile an AST for insert operations
Compute the capabilities.
Compute the capabilities. This should be overridden in subclasses as needed.
Create a (possibly specialized) ResultConverter for the given JdbcType.
Create a (possibly specialized) ResultConverter for the given JdbcType.
Create a DDLInvoker -- this method should be implemented by drivers as needed
Create a DDLInvoker -- this method should be implemented by drivers as needed
Create an InsertInvoker -- this method should be implemented by drivers as needed
Create an InsertInvoker -- this method should be implemented by drivers as needed
Gets the Slick data model describing this data source
Gets the Slick data model describing this data source
used to build the model, uses defaultTables if None given
logs unrecognized default values instead of throwing an exception
Create a (possibly specialized) ResultConverter for Option values of the given JdbcType.
Create a (possibly specialized) ResultConverter for Option values of the given JdbcType.
Create an executor -- this method should be implemented by drivers as needed
Create an executor -- this method should be implemented by drivers as needed
Jdbc meta data for all tables included in the Slick model by default
Jdbc meta data for all tables included in the Slick model by default
The MappingCompiler for this driver.
The MappingCompiler for this driver.
The external interface of this driver which defines the API.
The external interface of this driver which defines the API.
quotes identifiers to avoid collisions with SQL keywords and other syntax issues
quotes identifiers to avoid collisions with SQL keywords and other syntax issues
The table name for scalar selects (e.
The table name for scalar selects (e.g. "select 42 from DUAL;"), or None for
scalar selects without a FROM clause ("select 42;").
A collection of values for using the query language with a single import statement.
A collection of values for using the query language with a single import statement. This provides the driver's implicits, the Database and Session objects for DB connections, and commonly used query language types and objects.
Create a SQL representation of a literal value.
Create a SQL representation of a literal value.
(derbyDriver: StringAdd).self
(derbyDriver: StringFormat).self
(Since version 2.1) use createModel() instead (appending parenthesis)
(Since version 2.1) use defaultTables instead
(derbyDriver: ArrowAssoc[DerbyDriver]).x
(Since version 2.10.0) Use leftOfArrow instead
(derbyDriver: Ensuring[DerbyDriver]).x
(Since version 2.10.0) Use resultOfEnsuring instead
Slick driver for Derby/JavaDB.
This driver implements scala.slick.driver.JdbcProfile without the following capabilities:
Functions.databaseis not available in Derby. Slick will return an empty string instead.Sequence.currto get the current value of a sequence is not supported by Derby. Trying to generate SQL code which uses this feature throws a SlickException.zipandzipWithIndex. 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).