-
Notifications
You must be signed in to change notification settings - Fork 251
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
[DA] Planetscale engine tests: prisma_17103::regression #4480
Comments
Just did a manual run of In particular, the test
|
Update: #[connector_test(relation_mode = "foreignKeys")]
async fn regression(runner: Runner) -> TestResult<()> {
run_query!(
&runner,
r#"mutation {
createOneA(data: { id: 1, b: { create: { id: 1 } } }) {
id
}
}
"#
);
insta::assert_snapshot!(
run_query!(&runner, r#"mutation { updateOneB(where: { id: 1 }, data: { a: { connect: { id: 1 } } }) { id } }"#),
@r###"{"data":{"updateOneB":{"id":1}}}"###
);
Ok(())
} |
Update: the problem lies in how the number of affected rows is computed. When using the Without this, MySQL returns 0 affected row when performing a no-op update, but this breaks the Query Engine expectations when performing nested Problem: there is no known way of setting client connection flags in PlanetScale. We should reach out to them. |
This is a subcluster of failures after having enabled planetscale tests in #4423
Failing tests in this cluster:
Please follow this process
The text was updated successfully, but these errors were encountered: