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.
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.
Extension methods to generate the JDBC-specific insert actions.
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 InsertActionComposer that returns a mapping of the inserted and generated data.
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.
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.
An InsertActionComposer that returns generated keys or other columns.
An 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.
Extension methods to generate the JDBC-specific insert actions.
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 API for using the query language with a single import statement.
The API 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.
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 configuration for this driver, loaded via loadDriverConfig.
The configuration for this driver, loaded via loadDriverConfig.
Load the configuration for this driver.
Load the configuration for this driver. This can be overridden in user-defined driver subclasses to load different configurations.
The default implementation does a breadth-first search in the supertype hierarchy of the runtime class until it finds a class or trait matching "slick.driver.XXXDriver" where XXX is an arbitrary name, and then returns the path "slick.driver.XXX" from the application config, if it exists, otherwise an empty Config object.
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;").
Create a SQL representation of a literal value.
Create a SQL representation of a literal value.
(Since version 3.0) Use 'api' instead of 'simple' or 'Implicit' to import the new API
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.
(Since version 3.0) Use 'api' instead of 'simple' or 'Implicit' to import the new API
A generic driver for JDBC-based databases. This can be used as a fallback when a specific driver for a database is not available.
(Since version 3.0.0) JdbcDriver provides a generic implementation that needs to be customized for specific database systems; Use a concrete driver or implement and customize JdbcDriver yourself