Generated SQL identifier too long in 2.1b6

javamona · **Posted:** Mon Nov 10, 2003 9:09 pm

I am doing a select from a table, with an column called COLLECTORATE_CODE which is 17 characters long.
In version 2.0.3 the following SQL is generated.

select applicat0_.COLLECTORATE_CODE as COLLECTORATE_CODE,
[other columns .......] from TCC.APPLICATION applicat0_ where applicat0_.COLLECTORATE_CODE=?

When I switched to using 2.1b6 the following is generated
select applicat0_.COLLECTORATE_CODE as COLLECTORATE_CODE0_,
[other columns .......] from TCC.APPLICATION applicat0_ where applicat0_.COLLECTORATE_CODE=?

Now the alias for COLLECTORATE_CODE has 19 characters, which is too long for Informix 7, the database server that we are using.

gavin · **Posted:** Mon Nov 10, 2003 9:15 pm

uggghhhh. ummmm. what kind of mapping is collectorate_code? It must by the PK, I suppose....

javamona · **Posted:** Tue Nov 11, 2003 9:38 am

Yes. The mapping is as follows
<class
name="org.fsl.references.tcc.Application"
schema="TCC"
table="APPLICATION"
mutable="false">

<composite-id
name="applicationPK"
class="org.fsl.references.tcc.ApplicationPK" >

<key-property name="collectorateCode" column="COLLECTORATE_CODE" type="string" />
<key-property name="applicationNumber" column="APPL_SNO" type="integer"/>
<key-property name="year" column="YEAR_NBR" type="integer"/>

</composite-id>

<property name="trn" column="TRN_NBR" type="integer"></property>
<property name="branch" column="BRANCH_NBR" type="integer"></property>

</class>

gavin · **Posted:** Tue Nov 11, 2003 10:00 am

Damn this could be a problem. I don't recall making this change. Shit.

This gives me something to think about.

steve_molitor · **Joined:** Thu Nov 13, 2003 11:27 am **Posts:** 4

We're using Informix 7 with Hibernate 2.03 also. One issue that has always been a problem, even with 2.03, is joining where one column name is close to 18 characters long. For example, in a one-to-many relationship, etc. Hibernate generates a column alias that is longer than 18 characters in those cases.

I've been off-list for a while; any changes in the 2.1 beta alias generation that might help here?

Thanks.

gavin · **Posted:** Thu Nov 13, 2003 11:35 am

Nope, the problem still exists for identifier and discriminator columns.

steve_molitor · **Joined:** Thu Nov 13, 2003 11:27 am **Posts:** 4

How hard is it to fix? I looked into doing a patch a while ago; got a little lost looking at the code and gave up. Can't remember the details.

Where should I start looking?

gavin · **Posted:** Thu Nov 13, 2003 11:43 am

Yeah its hard. But you would be my best friend ;-) It really is one of our longest-running issues.

You basically "just" need to make generation of identifier column aliases work the same as other properties. Its possible, and it would be a good way to learn the internals of Hibernate.

Note that the implementation of the alias-generation stuff is NOT the greatest thing in Hibernate. Max hates it.

javamona · **Posted:** Thu Nov 13, 2003 3:37 pm

You'd be my best friend as well, as we'd like to move to 2.1 release when its ready, and if the 2.0.3 fails on one of the tables, we'd be screwed.

max · **Posted:** Thu Nov 13, 2003 5:05 pm

gavin wrote:

Max hates it.

It's black can't-see-through magic!

grosskop · **Joined:** Wed Nov 26, 2003 10:07 am **Posts:** 3

I am happy to find this subject. the analys matches exactly mine,
hibernate seems to shorten long columname aliases but fails to do so on id fields.
Has anyone come further in fixing this? Or do I have to start from the beginning if I want to resolve it? I am not familiar with the hibernate source, so I would be happy with any hint.

Quote:

It really is one of our longest-running issues

is there a bug registered? you know the number?

gavin · **Posted:** Thu Nov 27, 2003 12:46 pm

http://opensource.atlassian.com/project ... key=HB-244

max · **Posted:** Thu Nov 27, 2003 7:45 pm

Go there again - now with a possible patch ;)

If someone could test it I would appreciate it ;)