prisma: Support MySQL 8 (currently MySQL 8 is not supported)
(I am using a digitalocean mysql 8 instance) Right now the CLI doesn’t support MySQL 8 as it using an older client.
This might automatically be fixed with the introspection rewrite in Rust.
Also, lift is able to connect to the instance but it is unable to save migrations. It is able create the _Migrations table but when I run prisma lift save --name 'init' it is unable to save the migration in the file system and unable to create tables.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 18 (14 by maintainers)
Commits related to this issue
- Merge pull request #384 from Jolg42/fix-example-schema fix(photon): remove @unique for @id fields in examples Former-commit-id: 49c68f4cae7044ae27947761dcaef47def7bd8a0 — committed to prisma/prisma by timsuchanek 4 years ago
- Merge pull request #384 from Jolg42/fix-example-schema fix(photon): remove @unique for @id fields in examples Former-commit-id: 49c68f4cae7044ae27947761dcaef47def7bd8a0 Former-commit-id: 46f21b416ad... — committed to prisma/prisma by timsuchanek 4 years ago
I did some investigation and was able to confirm that for me, it happens only in the
prisma2 initflow with MySQL 8. The connection to the database at this stage is done on the typescript side and doesn’t go through the migration engine nor the introspection engine, as far as I could tell.I can also confirm the migration issue mentioned above is a separate bug, I’m working on fixing it.
Hi, @divyenduz. Thank you for your response. That’s a little disappointing but I really appreciate the transparency. 👍
(I was actually just using my comment to repeat this and make it explicit for everyone 😉 )