P
Prisma•6mo ago
Yagodi

Unable to create migrations at all

Hi I've been trying to create a baseline migration for my project and I keep getting an error that drift being detected. Prisma essentially proceeds to just say that my entire schema is brand new. The problem is that no, there is no drift. I tried everything I could like prisma db pull which indeed shows that everything is identical. I must create a migration because I now have a need for SQL triggers so I don't really have the option to just not use them. Also I cannot do a reset because there is a lot of data in said database I need it to work in production 😅 Thank you in advance!
2 Replies
Prisma AI Help
Prisma AI Help•6mo ago
You decided to hold for human wisdom. We'll chime in soon! Meanwhile, #ask-ai is there if you need a quick second opinion.
Yagodi
YagodiOP•6mo ago
PS C:\Users\Win\Documents\Github\app-prisma-schema> bunx prisma -v
Environment variables loaded from .env
prisma                  : 6.5.0
@prisma/client          : 6.5.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v22.16.0
TypeScript              : 5.8.3
Query Engine (Node-API) : libquery-engine 173f8d54f8d52e692c7e27e72a88314ec7aeff60 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli 173f8d54f8d52e692c7e27e72a88314ec7aeff60 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 6.5.0-73.173f8d54f8d52e692c7e27e72a88314ec7aeff60
Default Engines Hash    : 173f8d54f8d52e692c7e27e72a88314ec7aeff60
Studio                  : 0.510.0
Preview Features        : driverAdapters, relationJoins
PS C:\Users\Win\Documents\Github\app-prisma-schema> bunx prisma -v
Environment variables loaded from .env
prisma                  : 6.5.0
@prisma/client          : 6.5.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v22.16.0
TypeScript              : 5.8.3
Query Engine (Node-API) : libquery-engine 173f8d54f8d52e692c7e27e72a88314ec7aeff60 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine           : schema-engine-cli 173f8d54f8d52e692c7e27e72a88314ec7aeff60 (at node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm             : @prisma/prisma-schema-wasm 6.5.0-73.173f8d54f8d52e692c7e27e72a88314ec7aeff60
Default Engines Hash    : 173f8d54f8d52e692c7e27e72a88314ec7aeff60
Studio                  : 0.510.0
Preview Features        : driverAdapters, relationJoins
I doubt this is useful as this issue occurs on other environments as well Never mind I understand the exact purpose of migrations now I was just being stupid... I thought migrations could work like schemas where you can add new things and just push them to your database, but they're more intended to be used initially when creating it.

Did you find this page helpful?