This adds the first migration which reflects the database in its current state. This enables future deployments to properly initialize and configure a newly created database.
Note that this is a breaking change for existing setups as the database is already configured. The following steps must be taken to migrate:
Create a new table "migrations". If it already exists, and has rows, it must be backed up and cleared as the migrations must appear in the correct order.
The query for creating the table is: CREATE TABLE "migrations" ("id" SERIAL NOT NULL, "timestamp" int8, name varchar(255), PRIMARY KEY ("id")).
Insert the correct values in the rows timestamp and name, using the filename of the first migration. It should be
a. timestamp: 1641894827503
b. name: Initial1641894827503
Run the migrations (or start the backend). It should output "No migrations are pending"
This change, and the steps above, should be clearly described in the next release.
This adds the first migration which reflects the database in its current state. This enables future deployments to properly initialize and configure a newly created database.
Note that this is a breaking change for existing setups as the database is already configured. The following steps must be taken to migrate:
CREATE TABLE "migrations" ("id" SERIAL NOT NULL, "timestamp" int8, name varchar(255), PRIMARY KEY ("id")).1641894827503b. name:Initial1641894827503This change, and the steps above, should be clearly described in the next release.