[ https://issues.apache.org/jira/browse/DERBY-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561533#action_12561533 ]
Daniel John Debrunner commented on DERBY-3342: ---------------------------------------------- I noticed this because I was removing the last use of setNullability() for DERBY-2775. My change was in ConditionalNode and making it caused DatabaseMetaDataTest to fail and upon investigation actually make the nullability correct for column 9 LENGTH. Strange thing is that the LENGTH column 9 will not go through ConditionalNode, however columns 10 and 11 of the getProcedureColumns columns do involve a ConditionalNode, ie. a CASE expression. So this bug maybe an example of what DERBY-2775 is trying to solve, the state of one node accidentally changing another because they happen to share a reference to a mutable DataTypeDescriptor. > DatabaseMetaData.getProcedureColumns() returns incorrect nullability for > column 9 LENGTH > ---------------------------------------------------------------------------------------- > > Key: DERBY-3342 > URL: https://issues.apache.org/jira/browse/DERBY-3342 > Project: Derby > Issue Type: Bug > Components: JDBC, SQL > Affects Versions: 10.4.0.0 > Reporter: Daniel John Debrunner > > DatabaseMetaDataTest.testGetProceduresGetProcColumns asserts that column 9 > (LENGTH) is NULLABLE. (line 4364 of the test). > However the column comes directly from the internal virtual table > GetProcedureColumns which has its length column as not nullable (line 327 of > GetProcedureColumns.java). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.