I think new behavior is a bug... and should be addressed in the patch. Since there is no column name called 'SQLCol1' in the user querry, accepting an order by with that name is incorrect. Column names like these are generated names when there is no exposed name or alias provided for the result columns. Derby generates these names and should be hidden to the end user.
It should be easy to address this. You probably need to mark any new expressions you are adding as generated columns using* setNameGenerated(true)* call.
I'm not so sure - I thought expressions were given implementation dependent names that could be referenced in a sort key. In our case the name is "SQLCol1" so referencing that would be valid but non-portable.
I'm curious why ij is not labeling the columns that way and whether it should.
-- Jeremy
