Mark Woon wrote:
And I'd be more than happy to implement the fix, if I can just figure
out which methods are actually producing the offending SQL. I'll try
looking at it later tonight. I'm getting really tired of renaming my
db columns...
I think I've got a reasonable fix for this problem.
max wrote:
Another one is to rewrite the code that produces those aliases (and as
I remember - the logic are well-defined but unfortunatly not in a
single method).
That alias generation should of course use the Dialect class which
would have an getMaxColumnNameLength and getMaxTableNameLength.
Gavin King wrote:
Max, it would happen whenever you have a column name that approaches
the limit for the database. Hibernate needs to add an _0, etc at
the end when rendering aiases.
I know, would just be easier if he got a clean example :)
But Ok - I've fought with these kind of troubles before
nate Mailing List
> Subject: Re: [Hibernate] Length of Hibernate-generated aliases in SQL
>
>
> Could you give an hbm.xml and query example that gives that
> error ? (it
> would be nice to have some test scenario :)
> (especially, since it would be nice to know what one cou
Could you give an hbm.xml and query example that gives that error ? (it
would be nice to have some test scenario :)
(especially, since it would be nice to know what one could do to avoid
such a thing- it would also be a problem on db2 since it also has
some "weird" low limitations)
/max
Yi
Yick. The biggest design problem with Hibernate at present is
the fact that we have no single class responsible for rendering
SQL. (As I have mentioned before, Hibernate models SQL
statements using StringBuffer...) So little things like this
that should be *very* easy turn out to be way more tric
