Freeze
io.eezo.db.migrate.Freeze
object Freeze
Attributes
- Source
- Freeze.scala
- Graph
-
- Supertypes
- Self type
-
Freeze.type
Members list
Value members
Concrete methods
Attributes
- Source
- Freeze.scala
Attributes
- Source
- Freeze.scala
Attributes
- Source
- Freeze.scala
Attributes
- Source
- Freeze.scala
Attributes
- Source
- Freeze.scala
Attributes
- Source
- Freeze.scala
def write(name: String, resolutions: List[Resolution], newSnapshot: SchemaSnap, dbDir: Path = ...): Path
Attributes
- Source
- Freeze.scala
Concrete fields
Where a project keeps its migration history, relative to the working directory.
Where a project keeps its migration history, relative to the working directory.
Every entry point below takes the directory as a parameter defaulting to this, rather than reading it from a val. A hardcoded path is not a configuration problem so much as a testability one: with the path baked in, nothing that writes a migration can be exercised anywhere except the real db/ of whatever process is running.
Attributes
- Source
- Freeze.scala
In this article