[DERBY-6009] Need stricter checking of ORDER BY clause in VALUES expressions

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.9.1.0
• Fix Version/s: 10.10.1.1
• Component/s: SQL
• Labels: derby_backport_reject_10_9
• Issue & fix info: Repro attached
• Assignee: Dag H. Wanvik
• Reporter: Knut Anders Hatlen
• Created: 07/Dec/12 10:15
• Updated: 26/Jul/13 17:54
• Resolved: 03/Jan/13 04:07

Description

We only support column numbers in ORDER BY clauses in VALUES expression, as seen by this error message:

ij> values 1,2 order by 1+2;
ERROR 42878: The ORDER BY clause of a SELECT UNION statement only supports unqualified column references and column position numbers. Other expressions are not currently supported. (errorCode = 30000)

However, the checks let some unsupported expressions through and produce strange results. For example:

ij> values 1 order by 1+2;
1 |2
-----------------------
1 |3

1 row selected

It should probably have raised the same exception as the first query. And if not, the result should only have had one column.

And the next example should probably have raised a syntax error too, instead of a NullPointerException:

ij> values 1 order by int(1);
ERROR XJ001: Java exception: ': java.lang.NullPointerException'. (errorCode = 0)

Issue Links

• is related to: DERBY-6027 ORDER BY a cast expression gives NPE