Prisma upgrade

[paazmaya]

#200 lets see how to get this started...

So far just upgraded to v3 and formatted schemas to see if the tools can update, but putting this out here to get some visibility and possible direction.

Preview feature "atomicNumberOperations" is deprecated. The functionality can be used without specifying it as a preview feature.

Should there be a migration schema that removes this preview feature?

[paazmaya]

How is the type
data: Prisma.ProjectIdNameBrowserDeviceOsViewportCustomTagsBranchNameCompoundUniqueInput
at

backend/src/test-variations/test-variations.service.ts

Line 45 in 7a47481

data: Prisma.ProjectIdNameBrowserDeviceOsViewportCustomTagsBranchNameCompoundUniqueInput

generated?
Or what magic is this?

---

Solved it by 1c76246

[paazmaya]

I cannot get past npx prisma migrate dev, as it mentions:

Error: The migrations folder contains migration files from an older version of Prisma Migrate which is not compatible.
Read more about how to upgrade to the new version of Migrate:
https://pris.ly/d/migrate-upgrade

After removing the lock file from migrations folder, next issue arrives:

Error: P3015

Could not find the migration file at /Users/jukka.paasonen/github.com/backend/prisma/migrations/20200503001556-init/migration.sql. Please delete the directory or restore the migration file.

[pashidlos]

@paazmaya those types are generated from schema file
starting from Prisma v3 they completely changed that process and to migrate it require redo all DB schema from scratch

do you think it's possible to migrate already existing data in DB?
you could try to remove all migrations and make it as a breaking change

[paazmaya]

@pashidlos do you mean removing everything under prisma/migrations folder?

I am looking to continue by upgrading to Prisma v4, and it might be easier without the legacy migration files...

[paazmaya]

Continuing in #206