db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1633) Regression: The fields of views are not being calculated properly since 10.1.2.4
Date Wed, 16 Aug 2006 22:46:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]

A B updated DERBY-1633:
-----------------------

    Derby Info: [Existing Application Impact, Regression]  (was: [Existing Application Impact,
Patch Available, Regression])

Thank you Rick for the review and for the helpful comments.  I looked through the patch and
found two assumptions in the code: one explicit (which you also pointed out) in Predicate.skipRemap(),
and another implicit one in the "getScopedOperand()" method of BinaryRelationalOperatorNode.

It's the implicit assumption in getScopedOperand() that is the important one--and some initial
tracing shows that there may in fact be a problem in that area.  So thanks for bring this
up.

I am unchecking the "Patch Available" box as I look into the matter more.  In the meantime,
committers please note that this means d1633_v2.patch is NOT ready for commit after all. 
I will post more when I have a better idea of what's going on.  Thanks for everyone's patience
here...

> 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.0.0
>
>         Attachments: d1633_repro.sql, d1633_v1_reviewOnly.patch, d1633_v2.patch, DERBY-1633_v1.html,
DERBY-1633_v2.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

        

Mime
View raw message