[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4956) Native Query returns wrong results
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c...
]
Steve Ash commented on HHH-4956:
--------------------------------
Steve, you stated:
"Hibernate internals are built to extract values from ResultSets using names, not
indexes so thats not an option here."
It would seem that extracting based on indexes would be a solution to this particular
problem. Are you excluding it based on the economic cost in developing it given current
Hibernate internals? Or is there some other reason that I'm missing?
I was just bit by this myself, and can empathize with the challenge of inconsistent driver
support. I wonder if at least a defensive mechanism to fail such queries that result in
ambiguous result set column names would be "better" than returning incorrect
results?
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