Arvados

The easy fix (reject instead of ignoring) looks something like this, in source:services/api/lib/load_param.rb

     if @select
       # Any ordering columns must be selected when doing select,
       # otherwise it is an SQL error, so filter out invaliding orderings.
-      @orders.select! { |o|
+      @orders.each { |o|
         # match select column against order array entry
-        @select.select { |s| /^#{table_name}.#{s}( (asc|desc))?$/.match o }.any?
+        if not @select.select { |s| /^#{table_name}.#{s}( (asc|desc))?$/.match o }.any?
+          raise ArgumentError.new("Cannot order on '#{s}' when column excluded by select param")
+        end
       }
     end

IMO it would be vastly preferable to add the given column to the list of columns to select (without adding it to the list of attributes to return to the client). That might involve changing more than 2 lines of code, though.

I just got caught by this. Definitely was not expecting the selected columns to have any bearing on the requested order. Not really understanding why this is not a simple thing to do... must be some difficulties with the Ruby ORM?