[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2742?page=c...
]
Max Rydahl Andersen commented on HHH-2742:
------------------------------------------
provide a testcase with the full mapping for User too...names should not be aliased so i
guess its because you have other columns/properties mapped that you don't list.
Columns in resultset of stored procedure call are being aliassed
----------------------------------------------------------------
Key: HHH-2742
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2742
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.2.2
Environment: Hibernate version 3.2.2, Sybase
Reporter: Martin van Dijken
I have a call to a stored procedure that returns a result set, mapped as:
<sql-query name="loadUser" callable="true">
<return class="User">
<return-property name="id" column="userId"/>
<return-property name="fullName"
column="usersFullNameAsCitedWhenRegistering"/>
</return>
<query-param name="userId" type="long"/>
{call loadUser(:userId)}
</sql-query>
I get the error:
invalid column name 'usersFul5_12_0_'
It looks like although I mapped the field fullName in my user object to the field
usersFullNameAsCitedWhenRegistering in the resultset, Hibernate is determining that
usersFullNameAsCitedWhenRegistering is too long and aliasses that to usersFul5_12_0_. The
resultset however does not contain usersFul5_12_0_.
Can this be fixed somehow? If (probably) not, can you please document this in the
"calling stored procedure section" to save others a few hours of searching?
--
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