[hibernate-issues] [Hibernate-JIRA] Created: (HHH-6151) HQL with joins in sub-select creates wrong SQL (copy of NH-2648)
HQL with joins in sub-select creates wrong SQL (copy of NH-2648)
----------------------------------------------------------------
Key: HHH-6151
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6151
Project: Hibernate Core
Issue Type: Bug
Components: query-hql
Affects Versions: 3.6.3
Environment: Hib 3.6.3 final; SQL Server 2008
Reporter: Harald M. Müller
Priority: Critical
Attachments: HQL_MissingJoinInExists.zip
The following query is translated to wrong SQL - the join is missing from the sub-select:
s.createQuery(
"SELECT ROOT FROM hmm.Sheet AS ROOT " +
"WHERE (EXISTS (FROM hmm.Shelf AS inv " +
" left JOIN ROOT.Folder AS ROOT_Folder " +
" WHERE (((ROOT_Folder.Shelf) = (inv) AND inv.Id = 1)) )) " +
" AND ROOT.Name = 'SomeName'").list();
(The query was created by a HQL generator of ours - hence the superfluous parentheses).
The inner exception is:
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The multi-part identifier
"folder2_.Shelf" could not be bound.
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)
...
at
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:281)
at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208)
... at org.hibernate.loader.Loader.doList(Loader.java:2533)
... 30 more
and the (wrong) SQL is
declare @p1 int
set @p1=0
exec sp_prepexec @p1 output,NULL,N'select sheet0_.Id as Id2_, sheet0_.Name as Name2_,
sheet0_.Folder as Folder2_ from Sheet sheet0_ where (exists (select shelf1_.Id from Shelf
shelf1_ where folder2_.Shelf=shelf1_.Id and shelf1_.Id=1)) and
sheet0_.Name=''SomeName'''
select @p1
----
Since NHib 0.99 and in Hibernate, it has been possible to use joins inside subqueries. HQL
allows it, and therefore, it should produce correct SQL (both syntactically and
semantically). Actually, joins in subqueries are *necessary* if there are OR or NOT
operators inside the subquery (some simpler queries can be rewritten with all Joins at
top-level).
I consider this bug critical because there is no workaround for
* HQL generated for earlier NHib versions
* manual HQL that needs OR or NOT inside a subquery
* (I assume) the correct translation of Linq's .Any in the NHib.Linq provider
I have attached a test case that shows the behavior.
--
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....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira