[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1075) New parser "not exists" command bug

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-1075.
-------------------------------


Closing stale resolved issues

> New parser  "not exists" command bug
> ------------------------------------
>
>                 Key: HHH-1075
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1075
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.5, 3.1 rc2
>         Environment: Win XP + java 1.5 + Oracle 9
>            Reporter: Michał Raczyński
>            Assignee: Steve Ebersole
>             Fix For: 3.1 rc3
>
>
> It is possible, that some combinations of one-argument operators are not parsed correctly. I have found an example concerning "not exists" command:
> HQL:
> select d.id
> from Decret d
> where not exists (
> 	select d1
> 	from Decret d1
> 	) 
> is parsed with the new parser as
> select
>   decret0_.ID as col_0_0_ 
>  from
>   ZAPISY decret0_ 
>  where
>   not (exists (select				<===== should be (not exists ( !!!!!!!
>    decret1_.ID 
>   from
>    ZAPISY decret1_))
> while with the old parser it's ok:
> select
>   decret0_.ID as col_0_0_ 
>  from
>   ZAPISY decret0_ 
>  where
>   (
>    not exists(
>     select
>      decret1_.ID 
>     from
>      ZAPISY decret1_
>    )
>   )

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira