[hibernate-issues] [Hibernate-JIRA] Created: (HHH-5666) Missing table alias for one column in generated sql

[Jakub Jankowski (JIRA)]

Missing table alias for one column in generated sql
---------------------------------------------------

                 Key: HHH-5666
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5666
             Project: Hibernate Core
          Issue Type: Bug
    Affects Versions: 3.5.0-CR-2
         Environment: Hibernate 3.5.0-CR-2, MySQL
            Reporter: Jakub Jankowski


Column 'desc' in generated sql doesn't have table alias 'announceme0_' (unlike the rest of columns) which genereates error while executing.

Genereted sql:

select announceme0_.announcementID as announce1_1_0_, 
announceme0_.oceaneqID as oceaneqID1_0_, 
announceme0_.fileName as fileName1_0_, 
desc as desc1_0_ 
from test.announcement announceme0_ where announceme0_.announcementID=1

Mapping for the table:
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<!-- Generated 2010-09-01 12:28:56 by Hibernate Tools 3.1.0.beta4 -->
<hibernate-mapping>
    <class name="all.model.Announcement" table="announcement" catalog="test">
        <id name="announcementId" type="int">
            <column name="announcementID" />
            <generator class="assigned" />
        </id>
        <property name="oceaneqId" type="java.lang.Integer">
            <column name="oceaneqID" />
        </property>
        <property name="fileName" type="string">
            <column name="fileName" length="1024" />
        </property>
        <property name="desc" type="string">
            <column name="desc" length="1024" />
        </property>
        <set name="routeOnAnnouncements" inverse="true">
            <key>
                <column name="announcementID" />
            </key>
            <one-to-many class="all.model.RouteOnAnnouncement" />
        </set>
    </class>
</hibernate-mapping>

There's no such problem with other tables.

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira