[ http://issues.apache.org/jira/browse/DERBY-1633?page=comments#action_12429738 ] Rick Hillegas commented on DERBY-1633: --------------------------------------
Hi Army. Thanks for the new patch and the extensive explanation in this JIRA and in the code. I am inclined to check in this fix tomorrow unless someone objects. > Regression: The fields of views are not being calculated properly since > 10.1.2.4 > -------------------------------------------------------------------------------- > > Key: DERBY-1633 > URL: http://issues.apache.org/jira/browse/DERBY-1633 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.1.3.0, 10.1.3.1 > Environment: 2.8 GHZ dual PIV on Windows XP SP2, 2 GB memory > Reporter: Prasenjit Sarkar > Assigned To: A B > Fix For: 10.2.1.0 > > Attachments: d1633_repro.sql, d1633_v1_reviewOnly.patch, > d1633_v2.patch, d1633_v3_code.patch, d1633_v3_tests.patch, > DERBY-1633_v1.html, DERBY-1633_v2.html, DERBY-1633_v3.html > > > Database can be assumed to be same as in Derby - 1205 Jira issue > SELECT PORT1.PORT_ID FROM T_RES_PORT PORT1, T_VIEW_ENTITY2PORT ENTITY2PORT > WHERE ENTITY2PORT.PORT_ID = PORT1.PORT_ID > This works fine in 10.1.2.1 but fails thereafter complaining that Comparison > between INTEGER and CHAR is not supported > for some reason, it thinks one of the PORT_ID columns is a character, when in > reality both are integers. > SELECT DISTINCT > ZONE.ZONE_ID ZONE_ID, > PORT2ZONE.ZONE_MEMBER_ID > FROM > T_RES_ZONE ZONE left outer join T_VIEW_PORT2ZONE > PORT2ZONE on > ZONE.ZONE_ID = PORT2ZONE.ZONE_ID , T_RES_FABRIC > FABRIC > In this query, it is complaining that one of the columns is a VARCHAR and > cannot be compared to INTEGER, when clearly this is not the case... > Same issue -- 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
