Reynir Björnsson
bde3baec46
Each migration is, for the most part, a module that exposes expected database version numbers, command identifier and documentation. This results in all information about the migration and rollback are found in the module itself, and builder_migrations.ml only has to reference the module. Some migrations require foreign keys constraints are disabled. It is not possible to enable or disable foreign key constraints inside a transaction.
24 lines
758 B
OCaml
24 lines
758 B
OCaml
let old_version = 1L and new_version = 1L
|
|
let identifier = "2021-02-02"
|
|
let migrate_doc = "add index job_build_idx on build"
|
|
let rollback_doc = "rollback index job_build_idx on build"
|
|
|
|
open Rresult.R.Infix
|
|
|
|
let migrate _datadir (module Db : Caqti_blocking.CONNECTION) =
|
|
let job_build_idx =
|
|
Caqti_request.exec ~oneshot:true
|
|
Caqti_type.unit
|
|
"CREATE INDEX job_build_idx ON build(job)";
|
|
in
|
|
Grej.check_version ~user_version:1L (module Db) >>= fun () ->
|
|
Db.exec job_build_idx ()
|
|
|
|
let rollback _datadir (module Db : Caqti_blocking.CONNECTION) =
|
|
let q =
|
|
Caqti_request.exec ~oneshot:true
|
|
Caqti_type.unit
|
|
"DROP INDEX IF EXISTS job_build_idx"
|
|
in
|
|
Grej.check_version ~user_version:1L (module Db) >>= fun () ->
|
|
Db.exec q ()
|