Support MySQL 8 (currently MySQL 8 is not supported)
See original GitHub issue(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.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:18 (14 by maintainers)
Top Results From Across the Web
MySQL 8.0 Release Notes
Downgrade from MySQL 8.0 to MySQL 5.7, or from a MySQL 8.0 release to a previous MySQL 8.0 release, is not supported. The...
Read more >2.11.4 Changes in MySQL 8.0
Incompatible change: A MySQL storage engine is now responsible for providing its own partitioning handler, and the MySQL server no longer provides generic ......
Read more >Supported Platforms: MySQL Database
Important Platform Support Updates » ; Debian GNU/Linux 11 · Debian GNU/Linux 10 · Microsoft Windows Server ; x86_64 · x86_64 · Microsoft...
Read more >Upgrading to MySQL 8.0? Here is what you need to know...
Support for partitioned tables using non-native partitioning was deprecated in MySQL 5.7 and is removed in MySQL 8.0. These tables can be ...
Read more >Changes in MySQL 8.0.31 (2022-10-11, General Availability)
Microsoft Windows: Fixed all C++ deprecation warnings by not using ... InnoDB: InnoDB now supports parallel index builds, which improves ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I did some investigation and was able to confirm that for me, it happens only in the
prisma2 init
flow 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. 👍