Packages

•  package root

  edit this text on github

  edit this text on github

  Scala Language-Integrated Connection Kit

  This is the API documentation for the Slick database library. It should be used as an additional resource to the user manual.

  Further documentation for Slick can be found on the documentation pages.

  To the slick package list...

  Definition Classes

  root

•  package slick

  Definition Classes

  root

•  package jdbc

  Contains the abstract JdbcProfile and related code.

  Contains the abstract JdbcProfile and related code. This includes all JDBC-related code, facilities for Plain SQL queries, and JDBC-specific profile components.

  Definition Classes

  slick

•  trait MySQLProfile extends JdbcProfile with MultipleRowsPerStatementSupport

  Slick profile for MySQL.

  Slick profile for MySQL.

  This profile implements slick.jdbc.JdbcProfile without the following capabilities:

  • slick.jdbc.JdbcCapabilities.returnInsertOther: When returning columns from an INSERT operation, only a single column may be specified which must be the table's AutoInc column.
  • slick.sql.SqlCapabilities.sequenceLimited: Non-cyclic sequence may not have an upper limit.
  • slick.relational.RelationalCapabilities.joinFull: Full outer joins are emulated because there is not native support for them.
  • slick.jdbc.JdbcCapabilities.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.

  insertOrUpdate and insertOrUpdateAll use INSERT ... ON DUPLICATE KEY UPDATE, which MySQL applies to any unique key, not only the primary key. When the new row clashes with a different row on a unique non-key column, that other row is updated instead of the call failing, and since the update list includes the primary key columns (except AutoInc ones), it is given the new row's key. For a strict primary-key upsert, remove slick.jdbc.JdbcCapabilities.insertOrUpdate in a custom profile: insertOrUpdate then selects the row by primary key and runs an UPDATE or an INSERT, so a clash on another unique key fails with a duplicate-key error. insertOrUpdateAll is not supported without the capability.

  The default type for strings of unlimited length is "TEXT", falling back to "VARCHAR(254)" if a Default or PrimaryKey column option is set. This can be changed by overriding slick.jdbc.MySQLProfile.defaultStringType in 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.

  Definition Classes

  jdbc

•  class MySQLModelBuilder extends JdbcModelBuilder

  Definition Classes

  MySQLProfile

• Builders
• ColumnBuilder
• ForeignKeyBuilder
• IndexBuilder
• MySQLColumnBuilder
• MySQLPrimaryKeyBuilder
• MySQLTableNamer
• PrimaryKeyBuilder
• TableBuilder
• TableNamer

slick.jdbc.MySQLProfile.MySQLModelBuilder

MySQLTableNamer