MySQLProfile
Related Docs:
object MySQLProfile
| package jdbc
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 SELECT statements that can be used to check for the existing of primary keys supplied to an INSERT operation. Used by the insertOrUpdate emulation on databases that don't support this in a single server-side statement.
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.
Extension methods to generate the JDBC-specific insert actions.
Extension methods to generate the JDBC-specific insert actions.
Builder for INSERT statements.
Builder for INSERT statements.
An InsertActionComposer that returns a mapping of the inserted and generated data.
An InsertActionComposer that returns a mapping of the inserted and generated data.
Code generator phase for queries on JdbcProfile.
Code generator phase for queries on JdbcProfile.
Code generator phase for inserts on JdbcProfile.
Code generator phase for inserts on JdbcProfile.
A ResultConverterCompiler that builds JDBC-based converters.
A ResultConverterCompiler that builds JDBC-based converters. Instances of this class use mutable state internally. They are meant to be used for a single conversion only and must not be shared or reused.
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.
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.
Builder for UPDATE statements used as part of an insertOrUpdate operation on databases that don't support this in a single server-side statement.
Builder for UPDATE statements used as part of an insertOrUpdate operation on databases that don't support this in a single server-side statement.
(Since version 3.2) Use ProfileAction instead of DriverAction
(Since version 3.2) Use StreamingProfileAction instead of StreamingDriverAction
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 profile's implicits, the Database API 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 profile.
The capabilities supported by this profile. 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.
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.
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
Load the configuration for this profile.
Load the configuration for this profile. This can be overridden in user-defined 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 with a name matching "slick.[...]Profile" and then returns uses this name as a path in the application config. If no configuration exists at this path, an empty Config object is returned.
The MappingCompiler for this profile.
The MappingCompiler for this profile.
The configuration for this profile, loaded via loadProfileConfig.
The configuration for this profile, loaded via loadProfileConfig.
The compiler used for queries
The compiler used for queries
quotes identifiers to avoid collisions with SQL keywords and other syntax issues
quotes identifiers to avoid collisions with SQL keywords and other syntax issues
Run a query synchronously on the provided session.
Run a query synchronously on the provided session. This is used by DistributedProfile until we can make it fully asynchronous.
The table name for scalar selects (e.g.
The table name for scalar selects (e.g. "select 42 from DUAL;"), or None for
scalar selects without a FROM clause ("select 42;").
The compiler used for updates
The compiler used for updates
Create a SQL representation of a literal value.
Create a SQL representation of a literal value.
The external interface of this profile which defines the API.
The external interface of this profile which defines the API.
(Since version 3.2) Use the Profile object directly instead of calling .profile on it
Slick profile for MySQL.
This profile implements slick.jdbc.JdbcProfile without the following capabilities:
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_nextvalands_currval.The default type for strings of unlimited length is "TEXT", falling back to "VARCHAR(254)" if a
DefaultorPrimaryKeycolumn option is set. This can be changed by overridingslick.jdbc.MySQLProfile.defaultStringTypein application.conf.Note: Slick 3.2 also checks the old config path "slick.driver.MySQL" that was used by Slick 3.0 and 3.1, and logs a warning if anything is found there. Values from the old path are *not* used anymore. This deprecation warning will be removed in a future version.