AnthoLume/database/migrations
Evan Reichard e68dfc445f
All checks were successful
continuous-integration/drone/push Build is passing
feat(admin): adding user & importing
2024-05-18 16:47:26 -04:00
..
20240128012356_user_auth_hash.go feat(db): button up migrations 2024-02-01 20:05:35 -05:00
20240311121111_user_timezone.go fix(timezones): move from utc offsets to timezones 2024-03-11 22:20:21 -07:00
20240510123707_import_basepath.go feat(admin): adding user & importing 2024-05-18 16:47:26 -04:00
README.md feat(db): button up migrations 2024-02-01 20:05:35 -05:00

DB Migrations

goose create migration_name

Note

Since we update both the schema.sql, as well as the migration files, when we create a new DB it will inherently be up-to-date. We don't want to run the migrations if it's already up-to-date. Instead each migration checks if we have a new DB (via a value passed into the context), and if we do we simply return.