Closed pantharshit00 closed 4 years ago
Please update the title and description to something that matches a feature request @pantharshit00 - including the current broken behavior as well is obviously fine.
Now I think about it, I would rather mark this as a bug.
https://github.com/prisma/prisma2/issues/384 is already an FR for MySQL 8. We can just highlight one of the bugs of that here.
I tracked this down to a problem in the migration engine, I'll link the PR once it's open :)
edit: as promised — https://github.com/prisma/prisma-engine/pull/47
This can probably be closed?
Yes, we've been testing on MySQL 8 for a long time, and nobody reported MySQL 8-specific difficulties, so as far as I know we have first-class support for it.
(I am using a DigitalOcean MySQL 8 cluster)
When performing the
prisma2 lift save
operation, only the_Migrations
table and the actual migration is not perform on a MySQL 8 instance.Stack trace: