-
Notifications
You must be signed in to change notification settings - Fork 380
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
After upgrading from 7.0.0 to 8.0.2, SQL translation results are changed and this version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery'. #1903
Comments
Ah, the effects of this disruptive change. But I think I need another workaround, since MySQL does not allow the use of LIMIT clauses in subqueries of IN clauses |
@lauxjpn if there's a MySQL limitation around LIMIT within IN subqueries, it should be possible to write a post-processing visitor to convert such subqueries to EXISTS ones... The EF query pipeline may have some issues making this more difficult than it should be - let me know if you need any assistance. |
This issue also effects the openiddict package when using the PruneAsync function. ( The Pomelo provider is recommended by the author) |
@roji So you can give me a code example to solve this problem, thank you very much. |
Is there a solution to this problem? It is impossible to execute the method 'PruneAsync' in OpenIddict |
Steps to reproduce
After updating Pomelo.EntityFrameworkCore.MySql from 7.0.0 to 8.0.2, the following code now exits abnormally
The reason is that the SQL that used to use the EXISTS clause has been translated as an IN clause, and now uses the LIMIT clause in the IN clause.
Is there an option to revert to the previous (7.0.0) behavior?
The issue
Pomelo.EntityFrameworkCore.MySql 8.0.2
Pomelo.EntityFrameworkCore.MySql 7.0.0
Further technical details
MySQL version: 8.0
Operating system: docker / windows 11 10.0.22631
Pomelo.EntityFrameworkCore.MySql version: 7.0.0 / 8.0.2
Microsoft.AspNetCore.App version:
Other details about my project setup:
The text was updated successfully, but these errors were encountered: