-
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
RowNumberForPaging, two tables and columns with same name #5641
Comments
Most likely duplicate of #4739 |
Not sure if it is the same as #4739. That one produces a |
Both have same cause. The projections are incorrectly renamed while translating for row number paging. In this case it doesn't throw exception because the property which gets wrong value is same type is the other property . So incorrect result. It throws NRE in #4739 because null value is being assigned to non-null property. |
fixed in 11c18e6 |
Steps to reproduce
Without Paging:
The issue
OrderId and ArtId is the same after using RowNumberPaging.
Select in paged query: [t].[ID], [t].[ID] AS [c0], [t].[name] VS [b].[ID], [ba].[ID], [ba].[name]
Further technical details
EF Core version: RC2
SQL version: 2008 R2
The text was updated successfully, but these errors were encountered: