[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c... ] Maillefer Jean-David commented on HHH-4956: ------------------------------------------- The following example is maybe clearer (it uses postgresql's system table to avoid generating a db structure): A simple select using native query which should return the 10 first index names and the related table names: EntityManager em = ...; String query = "select c.relname, c2.relname" + " from pg_class c" + " join pg_index i on c.oid = i.indexrelid" + " join pg_class c2 on i.indrelid = c2.oid" + " where c.relkind = 'i'" + " order by c.relname" + " limit 10"; @SuppressWarnings("unchecked") List<Object[]> indexes = em.createNativeQuery(query).getResultList(); for (Object[] objects : indexes) { String indexName = (String) objects[0]; String relatedTableName = (String) objects[1]; System.out.println(indexName + "\t" + relatedTableName); } System.out.println(); The output is twice the index name on each row. The related table name is overridden by the index name. I think it's due to the use of the same column name. Is hibernate using internally the column names instead of their indexes to fill the resulting Object[] ? Adding an alias to the query is a workaround. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c... ] Michael Golowka commented on HHH-4956: -------------------------------------- I can confirm this issue on Hibernate 3.5.3-Final Example: a.amount = 600 b.amount = 500 SELECT a.amount, b.amount FROM A a JOIN B b; Returns: [600, 600] But if you query with different aliases like this: SELECT a.amount as aAmount, b.amount as bAmount FROM A a JOIN B b; Returns: [600, 500] I suspect that the result that hibernate is retrieving from the database is correct, but when it tries to map that result to a java array or object, it is failing because it is referencing the alias name, not the index number. -- 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

[ 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? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c... ] Snehesh Mitra commented on HHH-4956: ------------------------------------ Is there a work around for this issue. If aliases are treated as column names, this issue can be resolved. Currently aliases are not identified and it throws a Column not found SQlException. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4956?page=c... ] Maillefer Jean-David edited comment on HHH-4956 at 5/28/11 1:03 PM: -------------------------------------------------------------------- What do you mean by "Currently" ? A specific version of hibernate ? In my application, the aliases are correctly identified (thus the workaround works as expected). BTW, I think it's a design flaw to internally use column name as column identifier, since it's often the case to see the same column name occurring many times in a query (for example, "id" when joining many tables). Is there some plan to correct this in the (not necessarily near) future ? was (Author: jidehem): What do you mean by "Currently" ? A specific version of hibernate ? In my application, the aliases are correctly identified (thus the work around works as expected) -- 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