Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We fucked up real bad here:
We started using
prisma db push
to sync the prisma schema with the db, with the intention of moving to migrations "soon":Open-Assistant/docker/Dockerfile.prisma
Lines 1 to 10 in 000fb06
But we never did this (because we never needed it), now I wanted to add a new table to the database and realized that the infrastructure for something like this is not in place.
Here I created an initial migration from the already available db scheme, to be able to deploy this without losing any data, we would need to force prisma to mark this migration as applied (even though it is not)
The command is as follows:
So this means, we have to ssh into the production web container and run this command to have the ability to apply future migrations.
All the changes to the schema.prisma file are auto-formatting by the prisma vscode extension