[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2376) Query with fully qualified entity class fails
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2376?page=c...
]
Neukomm commented on HHH-2376:
------------------------------
The problem seems to be caused by the fact that LiteralProcessor.setSQLValue(...) chops
off the rest of the tree by setting the first child to null. My test cases both work fine
with hibernate 3.2.1ga
if the rest of the tree isn't chopped off. I just don't know if not chopping of
the rest of the tree has
any unwanted side effects - at least, the hibernate junit test suite still yields the same
result.
Query with fully qualified entity class fails
---------------------------------------------
Key: HHH-2376
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2376
Project: Hibernate3
Type: Bug
Components: query-hql
Versions: 3.2.1
Environment: Hibernate 3.2.1ga, HSQLDB 1.8.0.4
Reporter: Neukomm
Attachments: DiscriminatorTest2.java
We've recently ran into a problem while migrating from Hibernate 3.1.1 to Hibernate
3.2.1ga:
While queries against the class attribute still work, if the class is non-qualified, the
query fails if the
name is fully qualified.
e.g.
"from Person p where p.class = Person"
works fine while
"from Person p where p.class = org.hibernate.test.discriminator.Person"
fails.
I've attached a test case to illustrated the problem. It should work when it's
put into the
'discriminator' package of the hibernate junit test cases.
Both testcases work fine for hibernate versions up to and including 3.2.0cr2.
In later versions, specifically in 3.2.1ga, the test case that uses the fully qualified
class name
('testQueryWithPackage') fails.
--
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