[ http://issues.apache.org/jira/browse/DERBY-1774?page=comments#action_12434139 ] Robert Enyedi commented on DERBY-1774: --------------------------------------
Despite the fact that the latest 1.2.1.3 beta solves the initial NullPointerException, I still receive the exception for a more complicated query (see the attached selectStatement.sql). I did not have the time yet to simplify it, but the error log (error.new.log) shows that this time the exception is right from inside the bytecode generated for the prepared statement. I'm unable to reproduce it when the statement is directly executed. I know that it's difficult to find the source of this bug (I tried it myself), but maybe the stack trace is of any help. > NullPointerException when using COALESCE > ---------------------------------------- > > Key: DERBY-1774 > URL: http://issues.apache.org/jira/browse/DERBY-1774 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.2.1.0, 10.1.3.1 > Environment: Windows XP SP2, JRE 1.5.0_05 > Reporter: Robert Enyedi > Attachments: crtStmt.sql, derby.log, derby.log-proper, derby.new.log, > selectStatement.sql > > > I receive the following error when executing the attached file: > ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while > evaluating an expression. SQLSTATE: XJ001: Java exception: ': > java.lang.NullPointerException'. > I also attached the Derby log with the derby.language.logQueryPlan property > set to true. > The problem does not appear when running on JRE 1.4.2_06. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
