[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]
A B updated DERBY-1633:
-----------------------
Attachment: DERBY-1633_v1.html
d1633_v1_reviewOnly.patch
Attaching a detailed description of the issue that is causing this regression,
and a description of what I believe to be the correct fix. I'm also attaching
a first version of the patch that is for review only.
The reason the patch is for review only is that it does not yet have new test
cases for catching this regression in the future, and more importantly, because
there are some changes in the patch about which I am not very clear. So I'm
hoping someone out there who's familiar with predicate "remapping" can provide
some input to help clarify some things for me. A description of what I don't
yet understand is provided in section V of the document.
I plan to continue looking at this issue to try to finalize my understanding of
the changes, but in the meantime, other comments/reviews would be helpful.
The description of the problem, the fix, and my continuing questions can be
found in DERBY-1633_v1.html; the first patch (for review only) is
d1633_v1_reviewOnly.patch.
> 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
> Attachments: d1633_repro.sql, d1633_v1_reviewOnly.patch,
> DERBY-1633_v1.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
