Open huf1 opened 5 years ago
@hrf1 It looks it is related to the stable sort strategy by design. Is 'c' your entity key? Does it work if you set 'EnsureStableOrdering = false'? Thanks.
@hrf1 It looks it is related to the stable sort strategy by design. Is 'c' your entity key? Does it work if you set 'EnsureStableOrdering = false'? Thanks.
Same issue here. It does work when 'EnsureStableOrdering = false'. But we would like this option enabled. 'c' is not part of any entity key.
using Microsoft.AspNetCore.App 2.2.0 Microsoft.AspNetCore.OData 7.2.1 Microsoft.AspNetCore.OData.Versioning 3.2.4
I'm experiencing the same issue and have no clue why it's complaining about the column c (which is also not part of any entity key.
any plans to fix this?
This is getting serious, I am going to get fired because of this bug
still in version 7.5.6
Are there any plans to fix this?
i also need this fixed
Experiencing the same issue
i also need this fixed
When calling odata endpoint with $orderby and $top parameters, the generated SQL Statement is invalid. Invalid column name 'c'.
Assemblies affected
Microsoft.AspNetCore.OData 7.1.0
Reproduce steps
I'm calling for example: http://localhost:5000/odata/Test/Test()?$skip=0&$orderby=BusinessUnit%20desc&$top=50 to get a 'BusinessUnit' ordered list
The result SQL Statement on SQL Server Database is:
The statement orders by a column [c], which is not present
If the $top parameter is removed, it works.
Expected result
Resulting SQL Statement should be valid and return a ordered list by 'BusinessUnit'
Actual result
SQL Exception 'Invalid column name 'c'.' is thrown.