[jira] Updated: (OPENJPA-49) bad sql pushdown, should use inner joins but has no joins, just uses first entity

["Patrick Linskey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Linskey updated OPENJPA-49:
-----------------------------------

    Fix Version/s: 0.9.7

> bad sql pushdown, should use inner joins but has no joins, just uses first entity
> ---------------------------------------------------------------------------------
>
>                 Key: OPENJPA-49
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-49
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: query
>         Environment: Windows xp, db2, derby
>            Reporter: George Hongell
>             Fix For: 0.9.7
>
>         Attachments: failureEntities.jar
>
>
> 182 bad pushdown, should use inner joins but has no joins, just uses first entity
>  TEST182; select count(e) from EmpBean e, DeptBean d, EmpBean e1 
> 15469  TRACE  [main] openjpa.jdbc.SQL - <t 1094861122, conn 295440796> [0 ms] executing prepstmnt 582099634 SELECT COUNT(t0.empid) FROM EmpBean t0
> s/b
> select count(t0) FROM EmpBean t0 ,DeptBean t1 ,EmpBean t2 
>   [ FAILED 182- bucket = fvtfull, query = select count(e) from EmpBean e, DeptBean d, EmpBean e1  : 
>    EXPECTED(
>  TEST182; select count(e) from EmpBean e, DeptBean d, EmpBean e1 
> [500]
>  TEST182; 1 tuple ) 
>    ACTUAL(
>  TEST182; select count(e) from EmpBean e, DeptBean d, EmpBean e1 
> count(e) 
> ~~~~~~~~ 
>    10    
>  TEST182; 1 tuple) ]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.