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.
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
Jdbc meta data for all tables included in the Slick model by default
(Since version 2.1) use createModel() instead (appending parenthesis)
(Since version 2.1) use defaultTables instead