Amey Dhoke

Hello,

This is not causing any problem, just that I am curious to know.

Looks like the way hibernate code works is, it adds columns from the joined table and it adds the same columns again if type join is LEFT_OUTER_JOIN. (The logic is in selectFragment() method of OneToManyPersister class)
Looks like it is a bug but im not sure if there is any other purpose behind this logic.

Any idea ?


Thanks,
Amey

Hi,

I am facing a issue with the query generated by hibernate to load from database.

SELECT this_.id AS id25_1_,
this_.name AS name25_1_,
offices2_.legal_entity_id AS legal3_3_,
offices2_.id AS id3_,
offices2_.id AS id27_0_,
offices2_.name AS name27_0_,
offices2_.legal_entity_id AS legal3_27_0_
FROM cm.legal_entities this_
LEFT OUTER JOIN cm.offices offices2_ ON this_.id = offices2_.legal_entity_id;

Why is hibernate generating query with duplicate reference to offices2_.id ?

My hbm file for legal_entities table is -

<hibernate-mapping> <class name="LegalEntity" table="LEGAL_ENTITIES" schema="CM" lazy="false"> <id name="id" type="long"> <column name="ID" precision="22" scale="0"/> <generator class="sequence"> <param name="sequence">legal_entities_seq</param> </generator> </id> <property name="name" type="string"> <column name="NAME"/> </property> <bag name="offices" cascade="none" fetch="join" inverse="true" lazy="false" > <key column="LEGAL_ENTITY_ID"/> <one-to-many class="Office"/> </bag> </class> </hibernate-mapping>

And hbm for office is -

<hibernate-mapping> <class name="Office" table="OFFICES" schema="CM" lazy="false"> <id name="id" type="long"> <column name="ID" precision="22" scale="0"/> <generator class="sequence"> <param name="sequence">offices_seq</param> </generator> </id> <property name="name" type="string"> <column name="NAME"/> </property> </class> </hibernate-mapping>


Thanks in advance,
Amey