okay, scratch that, new question: > The migrat...
# prisma-migrate
b
okay, scratch that, new question:
The migration
20220204125655_rename_fields_add_new
was modified after it was applied.
This migration is from aaaages ago (February) so this is surprising, it comes up every time I try to migrate, I'd rather not clear my database just because of this, how can I resolve this?
👀 1
a
Hey Barnaby, What version of Prisma are you using? We have seen some issues related to that error in the past, but they should be fixed in newer version of Prisma.
b
Copy code
❯ prisma -v
Environment variables loaded from .env
prisma                  : 3.6.0
@prisma/client          : 3.6.0
Current platform        : windows
Query Engine (Node-API) : libquery-engine dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at C:\Users\southclaws\.fnm\node-versions\v16.13.0\installation\node_modules\prisma\node_modules\@prisma\engines\query_engine-windows.dll.node)
Migration Engine        : migration-engine-cli dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at C:\Users\southclaws\.fnm\node-versions\v16.13.0\installation\node_modules\prisma\node_modules\@prisma\engines\migration-engine-windows.exe)
Introspection Engine    : introspection-core dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at C:\Users\southclaws\.fnm\node-versions\v16.13.0\installation\node_modules\prisma\node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary           : prisma-fmt dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at C:\Users\southclaws\.fnm\node-versions\v16.13.0\installation\node_modules\prisma\node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash    : dc520b92b1ebb2d28dc3161f9f82e875bd35d727Studio                  : 0.440.0
I'm quite a bit out of date so time to upgrade! I'll let you know if the issue persists
🤞 1