The Hibernate 3.0alpha documentation in section 5.1.17 key states the following.
(3) property-ref (optional): Specifies that the foreign key refers to columns that are not the primary key of the orginal table. (Provided for legacy data.)
I want it to join like this,
sectiontim0_.
sss_dowid=sectiontim0_1_.sss_dowid
but, instead, it joins like this,
sectiontim0_.
sss_timesid=sectiontim0_1_.sss_dowid
i.e. it's still using the primary key from the first table instead of the one that I specified using a property-ref. It does so regardless of whether I specify the property-ref.
Is this a bug?
Also, why do I have to specify a property-ref? i.e. why can't I just specify a column name instead? I would rather specify a column because the column is only needed for the join.
Hibernate version: 3.0alpha
Mapping documents:
<?xml version="1.0"
encoding="UTF-8"?>
<!DOCTYPE hibernate-mapping
PUBLIC
"-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<hibernate-mapping>
<class name="SectionTime"
table="sss_times"
mutable="false">
<id name="id"
column="sss_timesid">
<generator class="native"/>
</id>
<property name="daysId"
column="sss_dowid"/>
<join table="sss_dow">
<key column="sss_dowid"
property-ref="daysId"/>
<property name="days"
column="name"/>
</join>
</class>
</hibernate-mapping>
Code between sessionFactory.openSession() and session.close():
SectionTime st = (SectionTime)s.get(SectionTime.class, 305084);
System.out.println(st);
Full stack trace of any exception that occurs:
No stack trace, the generated SQL just isn't what I'm expecting
Name and version of the database you are using:
Microsoft SQL Server 2000
The generated SQL (show_sql=true):
select sectiontim0_.sss_timesid as sss_time1_0_,
sectiontim0_.sss_dowid as sss_dowid5_0_,
sectiontim0_1_.name as name6_0_
from sss_times sectiontim0_
inner join sss_dow sectiontim0_1_ on sectiontim0_.sss_timesid=sectiontim0_1_.sss_dowid
where sectiontim0_.sss_timesid=?
Login
FAQ
Search
