2022-01-05 09:20:56 -06:00
#!/usr/bin/env bash
2022-03-17 18:10:46 -05:00
2022-05-16 12:35:00 -05:00
# Usage:
2023-12-08 14:59:53 -07:00
# ./create_migration.sh name of migration
# ./create_migration.sh "name of migration"
# ./create_migration.sh name_of_migration
2022-05-16 12:35:00 -05:00
2022-03-17 18:10:46 -05:00
set -euo pipefail
2023-12-01 16:11:10 -06:00
cat <<EOF
WARNING: Migrations now all run in a single transaction. This makes upgrades
safer, but means that 'ALTER TYPE resource_type ADD VALUE' cannot be used if the
enum value needs to be referenced in another migration.
This also means you should not use "BEGIN;" and "COMMIT;" in your migrations, as
everything is already in a migration.
An example way of the proper way to add an enum value:
CREATE TYPE new_logintype AS ENUM (
'password',
'github',
'oidc',
'token' -- this is our new value
);
ALTER TABLE users
ALTER COLUMN login_type DROP DEFAULT, -- if the column has a default, it must be dropped first
2023-12-08 14:59:53 -07:00
ALTER COLUMN login_type TYPE new_logintype USING (login_type::text::new_logintype), -- converts the old enum into the new enum using text as an intermediary
2023-12-01 16:11:10 -06:00
ALTER COLUMN login_type SET DEFAULT 'password'::new_logintype; -- re-add the default using the new enum
DROP TYPE login_type;
ALTER TYPE new_logintype RENAME TO login_type;
EOF
2022-05-27 20:15:19 +03:00
SCRIPT_DIR = $( dirname " ${ BASH_SOURCE [0] } " )
(
cd " $SCRIPT_DIR "
2022-01-05 09:20:56 -06:00
2022-05-27 20:15:19 +03:00
# if migration name is an empty string exit
[[ -z " ${ * } " ]] && ( echo "Must provide a migration name" && exit 1)
2022-01-05 09:20:56 -06:00
2022-05-27 20:15:19 +03:00
# " " && "-" -> "_"
title = " $( echo " ${ @ } " | tr "[:upper:]" "[:lower:]" | sed -E -e "s/( |-)/_/g" ) "
2022-05-16 12:35:00 -05:00
2022-05-27 20:15:19 +03:00
migrate create -ext sql -dir . -seq " $title "
2022-01-05 09:20:56 -06:00
2022-05-27 20:15:19 +03:00
echo "Run \"make gen\" to generate models."
)