OrderBy and ThenBy problem

I know that this came from EF6, but it is ugly construction. It is very difficult to do chain of method with conditions:

var items = db.Items;
if (condition1)
{
    items = items.OrderBy(x => x.Field1);
}
if (condition2)
{
    items = items.ThenBy(x => x.Field2); 
}

if condition1 is false, then ThenBy throw exception. There are no really need to call OrderBy first and ThenBy next. More convinient would be method AddOrderBy instead of that two. Or in addition for them.

[divega]

@anpete @MichaelKetting reading the whole thread I tend agree that the fact that queries returned from all operators are IOrderedQueryable<T> is less than ideal. Any thoughts on this?

[justserega]

You can do that yourself

I tried it and this is not work. DbQuery<T> realize both IQuerable<T> and IOrderedQuerable<T>. There are no way to realize was OrderBy called or not.

Magic of OrderBy -> ThenBy work on interfaces that they return and extend (as extensition method). It work only if you call them in one chain

var items = db.Items.OrderBy(x => x.Time).ThenBy(x => x.Name)

and broke in this scenario:

var items = db.Items.AsQueryable();
items = items.OrderBy(x => x.Time);
items = items.ThenBy(x => x.Name); // oops, it is not compiled