Hi I am wondering if it wouldn't be easier to use butler (or some lib alike) to abstract the sql code generation?
Thus instead of hibernate generating the sql statements as string it would generate an sql expression tree using butler primitives. An evaluate function then would generate "per jdbc provider" the sql string for wished statement.

Does anybody see reason not to do so?

Cedric

you mean hibernate should use butler internally ?

well, dude - have you looked at the code ? We are actually building most of the sql with a kinda sql-expression-like stuff. And having a dependency on yet-another-library is not our biggest wish for xmas.

If you are asking wether it's better to use butler instead of hibernate - then oh, well - you can probabably guess what i'll recommend ;)

As always: Use the right tool for the job. (and coincidentally most of my jobs the right tool have been hibernate ;)

I already use hibernate and it make the job even better than I could expect it for an ORM, congratulation !!!
Yes, internaly. OK, the Dialect class with sql package does roughly this on strings...sorry.

I was just looking for an easy syncronization method between heterogenous db, do you know any?
I read hibernate code in hope to find a Java RDB model and sql-db ready-to-use (Schema, Table, Row, Constraints, SQL expression not based on strings) and didn't found one..thus I look at butler?!?....and I now found them also in hibernate "mapping" and "sql" package , Lucky week;-)

Thanks a lot and all my best wishes for xmas

Ced'