DatabaseConfig

slick.basic.DatabaseConfig$
See theDatabaseConfig companion trait

Attributes

Companion:
trait
Source:
DatabaseConfig.scala
Graph
Supertypes
class Object
trait Matchable
class Any
Self type

Members list

Concise view

Value members

Concrete methods

def forConfig[P <: BasicProfile : ClassTag](path: String, config: Config, classLoader: ClassLoader): DatabaseConfig[P]

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. slick.driver.DerbyDriver$ for slick.jdbc.DerbyProfile$) are recognized and translated to the new names. This feature is deprecated and will be removed in a future release.

Attributes

classLoader

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.

config

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.

path

The path in the configuration file for the database configuration (e.g. foo.bar would find a profile name at config key foo.bar.profile) or an empty string for the top level of the Config object.

Source:
DatabaseConfig.scala
def forURI[P <: BasicProfile : ClassTag](uri: URI, classLoader: ClassLoader): DatabaseConfig[P]

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.

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.

Attributes

Source:
DatabaseConfig.scala