-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(schema-engine): don't query CHECK_CONSTRAINTS on MySQL <= 8.0.16 #4661
feat(schema-engine): don't query CHECK_CONSTRAINTS on MySQL <= 8.0.16 #4661
Conversation
// MySQL 5.6 and 5.7 do not have a CHECK_CONSTRAINTS table we can query. | ||
// MariaDB, although it supports check constraints, adds them unexpectedly. | ||
// E.g., MariaDB 10 adds the `json_valid(\`Priv\`)` check constraint on every JSON column; | ||
// this creates a noisy, unexpected diff when comparing the introspected schema with the prisma schema. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These comments are taken from schema-engine/sql-schema-describer/src/mysql.rs
.
WASM Size
|
CodSpeed Performance ReportMerging #4661 will not alter performanceComparing Summary
|
✅ WASM query-engine: no benchmarks have regressedFull benchmark report
After changes in f171d68 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, though would be better with a test I think (we discussed that adding a test would require an old version of the MySQL image)
Closes prisma/prisma#19775