-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Set the ordering as the identifier when translating VALUES #33436
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
roji
added a commit
to roji/efcore
that referenced
this issue
Mar 30, 2024
roji
added a commit
to roji/efcore
that referenced
this issue
Mar 30, 2024
roji
added a commit
to roji/efcore
that referenced
this issue
Mar 30, 2024
roji
added a commit
that referenced
this issue
Mar 31, 2024
See #33438 (comment) |
Decision: we won't backport this since the workaround is trivial (add AsEnumerable()), and this doesn't actually address the customer-reported issue (which is about Concat, whereas this fixed Union). If additional user reports come in, we can reconsider. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Our translation of inline collections to SQL ValuesExpression does not specify an identifier, making it impossible to use project in certain query contexts.
Flagged by @maumar in #33410 (comment)
The text was updated successfully, but these errors were encountered: