Timothy Messier
8caaf3e076
This refactors the schema package and subpackages to support editions.
An Edition is a collection of sql migrations. A given boundary binary
can have multiple migration editions. The `schema.Manager` is updated to
apply the necessary migrations in the correct order, leveraging an
Edition's priority to determine the order in which the separate Editions
are applied.
The sql migration files are now nested under a directory for the
edition.
This also switches from the generated code to using embed, which
eliminates the need for the `make migrations` target and the generated
code. As such this commit removes the target and generated code.
See:
https://pkg.go.dev/embed
29 lines
824 B
PL/PgSQL
29 lines
824 B
PL/PgSQL
begin;
|
|
|
|
-- kms_version_column() will increment the version column whenever row data
|
|
-- is inserted and should only be used in an before insert trigger. This
|
|
-- function will overwrite any explicit values to the version column.
|
|
create or replace function
|
|
kms_version_column()
|
|
returns trigger
|
|
as $$
|
|
declare
|
|
_key_id text;
|
|
_max bigint;
|
|
begin
|
|
execute format('SELECT $1.%I', tg_argv[0]) into _key_id using new;
|
|
execute format('select max(version) + 1 from %I where %I = $1', tg_relid::regclass, tg_argv[0]) using _key_id into _max;
|
|
if _max is null then
|
|
_max = 1;
|
|
end if;
|
|
new.version = _max;
|
|
return new;
|
|
end;
|
|
$$ language plpgsql;
|
|
|
|
comment on function
|
|
kms_version_column()
|
|
is
|
|
'function used in before insert triggers to properly set version columns for kms_* tables with a version column';
|
|
|
|
commit; |