[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c...
]
Steve Ebersole commented on HHH-4956:
-------------------------------------
I mean that, internally, Hibernate uses its notion of {{org.hibernate.type.Type}} to
extract values from result sets (and bind values to prepared statements, amongst other
responsibilities). Have a peek there for details if you wish. Essentially, all that code
expects to be told the column label(s)/name(s) to use for extraction, not index(es). So
yes there is a huge development effort in altering that. I do not have any problems with
changing that to rely on column index(es) instead, per se; however that leads to another
problem in that this extends into public APIs.
Native Query returns wrong results
----------------------------------
Key: HHH-4956
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956
Project: Hibernate Core
Issue Type: Bug
Components: query-sql
Affects Versions: 3.3.2
Environment: hibernate 3.3.2.GA , linux, oracle 10g, weblogic 10
Reporter: Akashdeep Saddi
Issue: In-case running native queries vai hibernate we have two technical ID's in the
select clause from join of two or more tables the value of all the id's is set to one
value.
Example
A.id = 1
B.id =2
select A.Id as A_ID, B.Id as B_ID from A, B where A.B_id = B.id will return 1,1 in the
result instead of 1,2
Resolution: Use Alias in-case more than one technical keys are part of select clause.
Above query works fine when changed as below
select A.Id , B.Id from A, B where A.B_id = B.id will return 1,2
--
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