You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just did a manual run of new::regressions::prisma_17103::prisma_17103::regression, prisma/prisma#17103 still happens on PlanetScale.
The original issue is closed, but it only referred to MySQL (we didn't support Driver Adapters back then).
In particular, the test new::regressions::prisma_17103::prisma_17103::regression fails with the following error:
Expected 1 records to be connected after connect operation on one-to-many relation 'AToB', found 0.
Update: the problem lies in how the number of affected rows is computed.
When using the mysql Rust driver, we set a special client connection flag, CLIENT_FOUND_ROWS (see PR), which forces MySQL to return the number of rows matching the possibly-implicit WHERE filter in INSERT and UPDATE operations.
Without this, MySQL returns 0 affected row when performing a no-op update, but this breaks the Query Engine expectations when performing nested connects, which expect the update to have had happened already.
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: