-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Sqlite: Using column from table being updated in left join predicate generates invalid SQL #28886
Comments
😠 The person on that issue is asking for our schema. We're just like users when we file issues on other repos 🤣 |
Not really. I don't think there is anything specific to schema there. It is like if some user file issue on us that |
This seems like it's the same as npgsql/efcore.pg#2478, which I worked around in npgsql/efcore.pg#2478. Note that this limitation blocks some fairly basic scenarios, like two inner joins. I've posted another comment on the SQLite issue, to clarify whether they intend to fix this or not. We can simply port my PostgreSQL workaround to SQLite to fix this. |
This doesn't seem to be a problem with MySQL/MariaDB (the test isn't skipped), @lauxjpn can you confirm? So this seems to be a problem with PostgreSQL and SQLite, and I worked around it in PostgreSQL (npgsql/efcore.pg#2554). We can wait to see if the SQLite folks react on their issue, and if users complain, we can consider bringing the same workaround from PG to SQLite. |
Yes, there are no issues with the |
Thanks @lauxjpn |
Test: Update_with_cross_join_left_join_set_constant
Now throws invalid SQL error earlier used to work. Change in PR #28884
Filed https://www.sqlite.org/forum/forumpost/09862e12c7
The text was updated successfully, but these errors were encountered: