SchemaUtils
Attributes
- Source
- SchemaUtils.scala
- Graph
-
- Supertypes
-
class Objecttrait Matchableclass Any
- Self type
-
SchemaUtils.type
Members list
Value members
Concrete methods
This method can be used to load alternative DDL scripts.
This method can be used to load alternative DDL scripts.
This utility method is intended to be used for testing only. For production, it's recommended to run any DDL statements before the system is started.
It will use the database settings found under jdbc-journal, or pekko-persistence-jdbc.shared-databases if configured so. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Value parameters
- script
-
the DDL script. The passed script can contain more then one SQL statements separated by a ; (semi-colon).
Attributes
- Source
- SchemaUtils.scala
This method can be used to load alternative DDL scripts.
This method can be used to load alternative DDL scripts.
This utility method is intended to be used for testing only. For production, it's recommended to run any DDL statements before the system is started.
It will use the database settings found under configKey, or pekko-persistence-jdbc.shared-databases if configured so. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Value parameters
- configKey
-
the database configuration key to use. Can be
jdbc-journalorjdbc-snapshot-store. - script
-
the DDL script. The passed
scriptcan contain more then one SQL statements. - separator
-
used to separate the different DDL statements.
Attributes
- Source
- SchemaUtils.scala
Creates the schema for both the journal and the snapshot table using the default schema definition.
Creates the schema for both the journal and the snapshot table using the default schema definition.
For information about the different schemas and supported databases consult https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#database-schema
This utility method is intended to be used for testing only. For production, it's recommended to create run DDL statements before the system is started.
This method will automatically detects the configured database using the settings from jdbc-journal config. If configured with use-shared-db, it will use the pekko-persistence-jdbc.shared-databases definition instead. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Attributes
- Source
- SchemaUtils.scala
Creates the schema for both the journal and the snapshot table using the default schema definition.
Creates the schema for both the journal and the snapshot table using the default schema definition.
For information about the different schemas and supported databases consult https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#database-schema
This utility method is intended to be used for testing only. For production, it's recommended to create run DDL statements before the system is started.
This method will automatically detects the configured database using the settings from configKey config. If configured with use-shared-db, it will use the pekko-persistence-jdbc.shared-databases definition instead. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Value parameters
- configKey
-
the database journal configuration key to use.
Attributes
- Source
- SchemaUtils.scala
Drops the schema for both the journal and the snapshot table using the default schema definition.
Drops the schema for both the journal and the snapshot table using the default schema definition.
For information about the different schemas and supported databases consult https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#database-schema
This utility method is intended to be used for testing only. For production, it's recommended to run any DDL statements before the system is started.
This method will automatically detects the configured database using the settings from jdbc-journal config. If configured with use-shared-db, it will use the pekko-persistence-jdbc.shared-databases definition instead. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Attributes
- Source
- SchemaUtils.scala
Drops the schema for both the journal and the snapshot table using the default schema definition.
Drops the schema for both the journal and the snapshot table using the default schema definition.
For information about the different schemas and supported databases consult https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#database-schema
This utility method is intended to be used for testing only. For production, it's recommended to run any DDL statements before the system is started.
This method will automatically detects the configured database using the settings from configKey config. If configured with use-shared-db, it will use the pekko-persistence-jdbc.shared-databases definition instead. See https://pekko.apache.org/docs/pekko-persistence-jdbc/current/index.html#sharing-the-database-connection-pool-between-the-journals for details.
Value parameters
- configKey
-
the database journal configuration key to use.
Attributes
- Source
- SchemaUtils.scala