scala.slick.driver.MySQLDriver
see ModelBuilder#Table#Column#default
Table model builder factory.
Table model builder factory. Override for customization.
currently unused
currently unused
Converts from java.
Converts from java.sql.Types to the corresponding Java class name (with fully qualified path).
Creates a Slick data model from jdbc meta data.
Creates a Slick data model from jdbc meta data. Foreign keys pointing out of the given tables are not included.
Table model builders
Table model builders
Table model builders indexed by meta data qualified name
Table model builders indexed by meta data qualified name
(modelBuilder: StringAdd).self
(modelBuilder: StringFormat).self
(modelBuilder: ArrowAssoc[ModelBuilder]).x
(Since version 2.10.0) Use leftOfArrow
instead
(modelBuilder: Ensuring[ModelBuilder]).x
(Since version 2.10.0) Use resultOfEnsuring
instead
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.