prisma: `prisma migrate resolve --applied` not working on new project, `migration ... could not be found.` when using PowerShell on Windows
[Edit by @janpio] Most recent update, see this comment: https://github.com/prisma/prisma/issues/17558#issuecomment-2037194817
As mentioned in another issue: Following the Tutorial to baseline a database when using prisma in a new project with an existing database leads to an error:
The final step npx prisma migrate resolve --applied 0_init leads to the following error:
Error: P3017
The migration 0_init could not be found. Please make sure that the migration exists, and that you included the whole name of >the directory. (example: “20201207184859_initial_migration”)
The database (in my case) is mssql - if it makes any difference. The steps before (pulling, generating, creating migrations-directory and creating diff-sql) are all successful.
I tried the following things:
- Putting folder in quotes:
npx prisma migrate resolve --applied "0_init" - Passing the complete path:
npx prisma migrate resolve --applied ./prisma/migrations/0_init - Passing the complete path with filename:
npx prisma migrate resolve --applied ./prisma/migrations/0_init/migration.sql - Changing into prisma-directory and executing command
- Changing into prisma/migrations-directory and executing command
- Renaming folder “0_init” to “20201207184859_initial_migration” (I know, it’s stupid) and running
npx prisma migrate resolve --applied 20201207184859_initial_migration
… to no avail.
For reference: Here is the relevant comment from the other issue:
Hi I'm facing the same issue as @mrunalhajare. Here is what I'm doing:
1. `npx prisma db pull` -- Populates schema.prisma correctly
2. `npx prisma generate` -- Success generating
3. `mkdir -p prisma/migrations/init`
4. `npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/init/migration.sql` -- Creates migration.sql file in prisma/migrations/init directory
5. `npx prisma migrate resolve --applied init` -- ERROR
> Error: P3017
>
> The migration init could not be found. Please make sure that the migration exists, and that you included the whole name of the directory. (example: "20201207184859_initial_migration")
NOTE: I did manually create `migration_lock.toml` before step 5 above, but I get the same error.
Anything I'm doing wrong?
_Originally posted by @simplypress in https://github.com/prisma/prisma/issues/11555#issuecomment-1331671279_
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 6
- Comments: 29 (7 by maintainers)
Commits related to this issue
- fix(deps): update prisma monorepo to v5.12.1 (#1017) [](https://renovatebot.com) This PR contains the following updates: | Package | C... — committed to huv1k/website by renovate[bot] 3 months ago
- fix(deps): update prisma monorepo to v5.12.1 (#536) [](https://renovatebot.com) This PR contains the following updates: | Package | Ch... — committed to simonknittel/sinister-incorporated by renovate[bot] 3 months ago
- fix(deps): update all non-major dependencies (#72) [](https://renovatebot.com) This PR contains the following updates: | Package ... — committed to cerbos/query-plan-adapters by renovate[bot] 2 months ago
Based on the excellent information that @notmyfiles provided, here is a reproduction repository that shows both a working and a non-working migration file: https://github.com/janpio/prisma-repro-17558 The cause seems to be when you use
migrate diffvia Powershell, which is the default in VS Code and I also assume IntelliJ.Maybe follow the steps in the README @notmyfiles to confirm. (Also for @kraighamady and @rahInoue - but you using VSCode and Intellij would fit nicely here of course)
We definitely need to fix
migrate resolvehere (and other commands that probably would have a problem with this file).Workaround
Based on the analysis it might be enough to change the codepage or encoding of the file from UTF-16 with BOM to UTF-8, with or without BOM. Notepad++ for example can do that for you and many other tools. Alternatively you can of course recreate the file with another terminal. Cmd worked fine for me.
This was fixed by changing the encoding of the generated
migration.sqlfile! I changed it toUTF-8and it works like a charm!I checked about the first 2 commands: I wrote it down in the wrong order, but did them in the correct order 🙃. Anyway, I tried everything again - once in the VSCode terminal (which uses powershell) and once outside VSCode using cmd.exe. The command
npx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sqlseems to be the culprit – VSCode/powershell lead to the error, cmd not. As you noticed: VSCode or powershell seem to use a different encoding. So eitherprisma migrate resolveor… diffhas to be fixed to deal with different encodings. Thanks for your detective work!@janpio I just deleted my migration.sql file and reran the last two commands from the quickstart and it worked. The key was I used Git Bash instead of PS or the default PS in VSCode.
I didn’t take a look at the encoding of the files, but just recreating the initial migration in bash did the trick.
you can also change the encoding format in vs code and run the command from your usual terminal, like mentioned below
If you’re using VsCode and your 0_init/migration.sql is in the wrong encoding you can:
got it from here https://github.com/prisma/prisma/issues/14762#issuecomment-1533177502
I could isolate the difference of your and my project, it is literally only the encoding of the file:
Somehow that is throwing us off. But I have a reproduction now thanks to your repository @notmyfiles - so we can investigate this. Thanks!
Ahh, creating the diff via VSCode is a good idea. Let me do that. I used cmd externally via Windows Terminal.
Update: Yep, that’s it.
We just released version 5.12.1 which includes a new option
--outputformigrate diff. It takes a file path, where the result of yourmigrate diffcommand output is written - so no more need to do> foo.sqlin PowerShell which was the source of this problem!The old command still works of course:
But instead you can - and should if you are using PowerShell! - now also use this:
Let me know if this solves the problem as well for you, as did changing the file encoding manually.
Check the location of your
schema.prismafile, seems like the migration folder should be relative to that file as follows:Correct options:
It will fail if you mix the above locations. E.g.:
That solved it for me, good luck!
I can confirm it’s the file encoding as well.
After changing it to “Windows 1252”, the issue goes away.
I am experiencing the same issue, but it only occurs with IntelliJ IDEA. I followed these steps:
nest new check-prismacd check-prismanpm install prisma --save-devnpx prisma initnpx prisma db pullmkdir -p prisma/migrations/0_initnpx prisma migrate diff --from-empty --to-schema-datamodel prisma/schema.prisma --script > prisma/migrations/0_init/migration.sqlnpx prisma migrate resolve --applied 0_initI only executed these commands above. In Visual Studio Code, applying “0_init” was successful, but in IntelliJ IDEA, it failed. I tried these steps on a Windows PC and PowerShell.
Worked for me, thanks!!
This worked for me, thanks!
I faced similar issue when using powershell. Try the command from git bash it works.
npx prisma migrate resolve --applied 0_initYes, it only due to the encoding issue.
Thank you for investigating! I have tried the prisma db pull in various databases, but some encodings have caused character corruption in IntelliJ. This may be the same cause. If it continues, I will report back again. Thank you!