From: Mark W. <mor...@SM...> - 2003-01-04 04:53:33
|
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. > If the aliases generated exceeds that amount "do something" :) > > Maybe we should just postfix the names with 0_ instead of prefixing > them with _0 (and then chop them of with the dialects max lengths..) - > that would > make them unique ....and avoid name colisions (as long as the max > lenght is not near 3-4 chars ....) I think you meant prefix the names with 0_ and postfixing them with _0... ;) But yeah, I think this is an extremely simple solution to the problem. 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... -Mark |