[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1720?page=all ]
Mike Ringrose updated HHH-1720:
-------------------------------
Attachment: queryloader_patch.txt
This also fixes this issue by using the supplied loadable objects when creating a return
row of values. Sorry for posting two patches, but both alleviate this issue; hopefully
they are sufficient.
Incorrect Results from multi-valued query containing one-to-one
---------------------------------------------------------------
Key: HHH-1720
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1720
Project: Hibernate3
Type: Bug
Components: query-hql
Versions: 3.1.3
Environment: Hibernate 3.1.3, Oracle 10
Reporter: Mike Ringrose
Attachments: Record.hbm.xml, RecordRegistry.hbm.xml, dotnode_patch.txt,
queryloader_patch.txt
The Query below used to work correctly when using the classic query translator; however,
no long returns the correct results with the ast query translator. WIth the ast query
translator, the third result from the select, which is a one-to-one, always returns null
even when the value exists.
SELECT t.nameFirst, t.nameLast, t.registryRecord FROM Record t WHERE t.recordId =
?").setLong(0, 1);
Running the query below with the ast query translator, works fine and always returns the
correct results, that's why I beleive the problem to be only with multi-valued
queries.
SELECT t.registryRecord FROM Record t WHERE t.recordId = ?").setLong(0, 1);
The code between session open and close is below:
return (Object[])session.createQuery("SELECT t.recordId, t.registryRecord FROM
com.imsweb.seerdms.shared.entity.Record t WHERE t.recordId = ?").setLong(0,
1).uniqueResult();
--
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