Databases
StackOverflow2013
Postsdbo
POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
    primarykey
    data
    text
    <p>I have a stored proc that consists of 3 queries joined by unions. This works. It currently has an order by value set like so:</p> <pre><code> ORDER BY [CategoryTypeID], [SortOrder], [Name] </code></pre> <p>I want to make this dynamic so i tried using a case statement like this:</p> <pre><code> ORDER BY CASE WHEN @sort = 0 then [CategoryTypeID] ELSE [SortOrder] end </code></pre> <p>However, when i do this sql complains that order by items must appear in the select list if the statement contains union... etc</p> <p>However, if i change the above to avoid using the parameter:</p> <pre><code>ORDER BY CASE WHEN 0 = 0 then [CategoryTypeID] ELSE [SortOrder] end </code></pre> <p>That works. Why is it unhappy when i use a parameter when that parameter is not actually being used in the order by? I even tried including the parameter in the select statements but it still gave me the same error.</p> <p>I also tried doing case @sort when 1 etc but got the same results. And I did declare the parameter in my stored proc - @sort int = 0</p> <p>This is MSSQL 2012 express</p> <p>Edit - for additional clarity</p> <pre><code> ORDER BY CASE WHEN @sort = 0 then [SortOrder] ELSE [CategoryTypeID] end </code></pre> <p>and</p> <pre><code>ORDER BY CASE WHEN @sort = 0 then [CategoryTypeID] ELSE [CategoryTypeID] end </code></pre> <p>Both of those statements fail as well with a 'must appear in the select list' error. And i was not trying to use both of those statements at the same time. Just giving them as examples that the columns themselves dont appear to be an issue. It using the parameter that appears to be an issue, even though the paramter itself is not being selected or being sorted.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmerk
    1. USmerk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat is in your SELECT list though..? You need to actually _select_ this.
      singulars
      1. POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
      1. USBen
    2. COBecause `ELSE` is never reached in the second case, so SQL Server acts as if it's not there. Try changing it to `WHEN 1 = 0`. Is `SortOrder` in your `SELECT` list? If not, why not?
      singulars
      1. POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
      1. USAaron Bertrand
    3. COSorry if i wasnt clear - if you look at the first sample line of code, that works. Meaning, all 3 of those columns are in the select. So it doesn't matter if the else is never reached or not. I could swap which column is in the else and get the same results. For some reason it just doesn't like the paramter being used
      singulars
      1. POOrder by with case statement fails only when using a parameter with error ORDER BY items must appear in the select list
      1. USmerk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload