JdbcProfile
The back-end type required by this profile
The back-end type required by this profile
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.
An InsertInvoker that returns the number of affected rows.
An InsertInvoker that returns the number of affected rows.
Pseudo-invoker for running DELETE calls.
Pseudo-invoker for running DELETE calls.
An InsertInvoker that can also insert from another query.
An InsertInvoker that can also insert from another query. This is supported for inserts which return the row count or the generated keys but not mappings which involve the original data that has been inserted (because it is not available on the client side).
Extension methods to generate the JDBC-specific insert actions.
Extension methods to generate the JDBC-specific insert actions.
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
The JDBC-specific InsertInvoker with additional methods
An InsertActionComposer that returns a mapping of the inserted and generated data.
An InsertActionComposer that returns a mapping of the inserted and generated data.
An InsertInvoker that returns a mapping of inserted values and generated keys.
An InsertInvoker that returns a mapping of inserted values and generated keys.
Build a Slick model from introspecting the jdbc meta data.
Build a Slick model from introspecting the jdbc meta data. Similar to SlickCodeGenerator, this is implemented as nested classes, which allow hooking into the behavior by overriding methods. This comes at the price of very tight coupling. In most cases you are better of transforming the generated model instead of overriding functionality here. It is only useful, if you need easy access to the jdbc meta data in order to influence how the model is generated. A good use case would be interpreting column types or default values Slick doesn't understand out of the box. If you just want to remove or hard code some default values, just transform the resulting model instead.
The tight coupling can easily lead to sorce code incompatibilities in future versions. Avoid hooking in here if you don't have to.
The type of query executors returned by the driver
The type of query executors returned by the driver
An Invoker for queries.
An Invoker for queries.
An InsertActionComposer that returns generated keys or other columns.
An InsertActionComposer that returns generated keys or other columns.
An InsertInvoker that returns generated keys or other columns.
An InsertInvoker that returns generated keys or other columns.
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.
A schema description contains the SQL statements for creating and dropping database entities. Schema descriptions can be combined for creating or dropping multiple entities together, even if they have circular dependencies.
Extension methods to generate the JDBC-specific insert actions.
Extension methods to generate the JDBC-specific insert actions.
Pseudo-invoker for running UPDATE calls.
Pseudo-invoker for running UPDATE calls.
The implicit values and conversions provided by this driver.
The implicit values and conversions provided by this driver.
This is a subset of simplesimple._ instead of using Implicit.
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 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 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 compiler used for deleting data
The compiler used for deleting data
The compiler used for inserting data
The compiler used for inserting data
The compiler used for queries
The compiler used for queries
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.
The compiler used for updates
The compiler used for updates
(Since version 2.1) use createModel() instead (appending parenthesis)
(Since version 2.1) use defaultTables instead
A profile for accessing SQL databases via JDBC. All drivers for JDBC-based databases implement this profile.