Load a profile and database configuration from the URI specified in a StaticDatabaseConfig annotation in the static scope of the caller.
Load a profile and database configuration from the URI specified in a StaticDatabaseConfig annotation in the static scope of the caller.
Load a Profile and database configuration through Typesafe Config.
Load a Profile and database configuration through Typesafe Config.
The following config parameters are available:
profile
(String, required): The fully qualified name of a class or object which
implements the specified profile. If the name ends with $
it is assumed to be an object
name, otherwise a class name.db
(Config, optional): The configuration of a database for the profile's backend.
For profiles extending JdbcProfile
(which always use JdbcBackend
), see
JdbcBackend.DatabaseFactory.forConfig
for parameters that should be defined inside of
db
.Note: Slick 3.2 also supports the old driver
parameter as an alternative to profile
.
Old profile names (e.g.
for slick.driver.DerbyDriver$
) are
recognized and translated to the new names. This feature is deprecated and will be removed
in a future release.
slick.jdbc.DerbyProfile$
The path in the configuration file for the database configuration (e.g. foo.bar
would find a profile name at config key foo.bar.pfoile
) or an empty string
for the top level of the Config
object.
The Config
object to read from. This defaults to the global app config
(e.g. in application.conf
at the root of the class path) if not specified.
The ClassLoader to use to load any custom classes from. The default is to try the context ClassLoader first and fall back to Slick's ClassLoader.
Load a profile and database configuration from the specified URI.
Load a profile and database configuration from the specified URI. If only a fragment name
is given, it is resolved as a path in the global app config (e.g. in application.conf
at
the root of the class path), otherwise as a path in the configuration located at the URI
without the fragment, which must be a valid URL. Without a fragment, the whole config object
is used.