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
Query: Exception when using OrderBy and navigation ("A column has been specified more than once in the order by list") #5427
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
maumar
changed the title
Query :: bug template
Query :: A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation
May 19, 2016
anpete
added a commit
that referenced
this issue
Jun 30, 2016
Fix: #3676 - Usage of the "let" keyword breaks grouping. - Fixed compiler bug in tracked, grouped queries. Fix: #5427 - A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation. - Fixed bug in SelectExpression.PrependToOrderBy Fix: #4539 - Query :: Join flattening fails for some complex cases involving SelectMany - SelectMany after GroupJoin should not cause client-eval. Also addressed most of the R# warnings in nav. rewriter.
anpete
added a commit
that referenced
this issue
Jun 30, 2016
Fix: #3676 - Usage of the "let" keyword breaks grouping. - Fixed compiler bug in tracked, grouped queries. Fix: #5427 - A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation. - Fixed bug in SelectExpression.PrependToOrderBy Fix: #4539 - Query :: Join flattening fails for some complex cases involving SelectMany - SelectMany after GroupJoin should not cause client-eval. Also addressed most of the R# warnings in nav. rewriter.
anpete
added a commit
that referenced
this issue
Jun 30, 2016
Fix: #3676 - Usage of the "let" keyword breaks grouping. - Fixed compiler bug in tracked, grouped queries. Fix: #5427 - A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation. - Fixed bug in SelectExpression.PrependToOrderBy Fix: #4539 - Query :: Join flattening fails for some complex cases involving SelectMany - SelectMany after GroupJoin should not cause client-eval. Also addressed most of the R# warnings in nav. rewriter.
anpete
added a commit
that referenced
this issue
Jul 1, 2016
Fix: #3676 - Usage of the "let" keyword breaks grouping. - Fixed compiler bug in tracked, grouped queries. Fix: #5427 - A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation. - Fixed bug in SelectExpression.PrependToOrderBy Fix: #4539 - Query :: Join flattening fails for some complex cases involving SelectMany - SelectMany after GroupJoin should not cause client-eval. Also addressed most of the R# warnings in nav. rewriter.
anpete
added a commit
that referenced
this issue
Jul 3, 2016
Fix: #3676 - Usage of the "let" keyword breaks grouping. - Fixed compiler bug in tracked, grouped queries. Fix: #5427 - A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation. - Fixed bug in SelectExpression.PrependToOrderBy Fix: #4539 - Query :: Join flattening fails for some complex cases involving SelectMany - SelectMany after GroupJoin should not cause client-eval. Also addressed most of the R# warnings in nav. rewriter.
anpete
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Jul 8, 2016
rowanmiller
changed the title
Query :: A column has been specified more than once in the order by list thrown for a complex query with orderby and navigation
Query: Exception when using orderby and navigation ("A column has been specified more than once in the order by list")
Jul 21, 2016
divega
changed the title
Query: Exception when using orderby and navigation ("A column has been specified more than once in the order by list")
Query: Exception when using OrderBy and navigation ("A column has been specified more than once in the order by list")
Sep 13, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
QueryNavigationsTest -> Collection_select_nav_prop_first_or_default_then_nav_prop_nested_with_orderby throws
Exception:
System.Data.SqlClient.SqlException : A column has been specified more than once in the order by list. Columns in the order by list must be unique.
query plan:
The text was updated successfully, but these errors were encountered: