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] Resolved: (DERBY-1633) Regression: The fields of views are not being calculated properly since 10.1.2.4
Date Mon, 28 Aug 2006 16:10:25 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]

A B resolved DERBY-1633.
------------------------

    Fix Version/s: 10.1.3.2
                       (was: 10.1.4.0)
       Resolution: Fixed
       Derby Info: [Existing Application Impact, Regression]  (was: [Patch Available, Existing
Application Impact, Regression])

Many thanks to Rick and to Mike for porting this fix back to 10.2 and 10.1, respectively.

I confirmed that the change is in 10.1 and als in the latest 10.2 beta snapshot.  Also, the
new test cases in lang/predicatePushdown.sql run correctly in both codelines.  Since this
fix is now in trunk, 10.2, and 10.1, I'm marking it resolved and clearing the "patch available"
flag.

Thanks also to Rick for taking the time to review the different iterations of this rather
involved patch.  I appreciate your time!

> 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.1.3.2, 10.2.1.0, 10.3.0.0
>
>         Attachments: d1633_10_1_merge.patch, 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

        

Mime
View raw message