-
Notifications
You must be signed in to change notification settings - Fork 225
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
Remove reference to EF-internal TpcTablesExpression #2387
Comments
I am already working on this. Many edge cases but it will be done in 7.0 |
Thanks @smitpatel, no rush as I said, I have no problem even shipping like this. |
smitpatel
added a commit
to dotnet/efcore
that referenced
this issue
Jun 1, 2022
- Apply pruning on subqueries in set operation when not distinct - Avoid table aliases which would be pruned in TPC later - Avoid push down when left-joining with TPC select expression Resolves npgsql/efcore.pg#2387 Resolves #28009
smitpatel
added a commit
to dotnet/efcore
that referenced
this issue
Jun 1, 2022
- Apply pruning on subqueries in set operation when not distinct - Avoid table aliases which would be pruned in TPC later - Avoid push down when left-joining with TPC select expression Resolves npgsql/efcore.pg#2387 Resolves #28009
smitpatel
added a commit
to dotnet/efcore
that referenced
this issue
Jun 1, 2022
- Apply pruning on subqueries in set operation when not distinct - Avoid table aliases which would be pruned in TPC later - Avoid push down when left-joining with TPC select expression Resolves npgsql/efcore.pg#2387 Resolves #28009
ghost
pushed a commit
to dotnet/efcore
that referenced
this issue
Jun 2, 2022
- Apply pruning on subqueries in set operation when not distinct - Avoid table aliases which would be pruned in TPC later - Avoid push down when left-joining with TPC select expression Resolves npgsql/efcore.pg#2387 Resolves #28009
This was done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #2366, I added NpgsqlSetOperationTypeResolutionCompensatingExpressionVisitor, which adds an explicit convert node on the leftmost set operation operand, to work around problematic PG type inference behavior.
At the moment, this visitor needs to visit the EF-internal TpcTablesExpression. @smitpatel will be looking at changes on the EF side to obviate this. This is non-critical.
The text was updated successfully, but these errors were encountered: