[teiid-issues] [JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935302#comment-12935302 ] 

RH Bugzilla Integration commented on TEIID-2458:
------------------------------------------------

Filip Nguyen <fnguyen at redhat.com> changed the Status of [bug 996550|https://bugzilla.redhat.com/show_bug.cgi?id=996550] from ON_QA to VERIFIED
                
> Sybase15 subquery using HAVING clause failing
> ---------------------------------------------
>
>                 Key: TEIID-2458
>                 URL: https://issues.jboss.org/browse/TEIID-2458
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector
>    Affects Versions: 7.7
>            Reporter: Van Halbert
>            Assignee: Steven Hawkins
>
> Example query is failing:  SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20)
> When this query is submitted through EDS using Squirrel or BQT as a client it returns:
> IntKey        StringKey
> 20              20                 0
> When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned.
> SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15
> RESULTS
> IntKey        StringKey
> 20              20                 0
> However, when the GROUP BY is removed from the query it returns the expected results as shown below:
> IntKey	StringKey	
> 20	   20	    -4
> The supporting VDB can be provided if needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira