[DERBY-6027] ORDER BY a cast expression gives NPE

• 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
• Bug behavior facts: Wrong query result
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 30/Dec/12 02:41
• Updated: 28/Jul/13 04:57
• Resolved: 08/Jan/13 07:16

Description

The following gives a NPE:

ij> values 1,2 order by int(1);

or

ij> select * from sysibm.sysdummy1 order by int(1);

The NPE happens when pulling up the order by expression seemingly due to a compiler phase problem:

Caused by: java.lang.NullPointerException
at org.apache.derby.impl.sql.compile.CastNode.getConstantValueAsObject(CastNode.java:851)
at org.apache.derby.impl.sql.compile.OrderByColumn.isReferedColByNum(OrderByColumn.java:466)
at org.apache.derby.impl.sql.compile.OrderByColumn.pullUpOrderByColumn(OrderByColumn.java:403)
at org.apache.derby.impl.sql.compile.OrderByList.pullUpOrderByColumns(OrderByList.java:195)
at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(CursorNode.java:254)

The variable sourceCTI is (still) null; being set by CastNode# bindCastNodeOnly, which presumably hasn't yet been run.

Issue Links

• relates to: DERBY-6009 Need stricter checking of ORDER BY clause in VALUES expressions