Hello!

I would like to know how I can get to the translated query... That is, I belive, QueryTranslator.sqlString

Basically, I want to create queries using Hibernate, but eventually run them using the SQL statements only, without Hibernate.

Any ideas?

Thanks,

Daniel

That's wierd idea, why do you need that ?

QueryTranslator is a good starting point

Simple, performance. What I have designed is a report engine that uses business objects, with relationships etc.

This is fine and dandy when designing the report, but I would much prefer the "final" query to be JDBC only, so I will avoid the configuration startup and query translation at runtime.

Hibernate at design time, jdbc at run time :)

However, I wouldn't know how to use the QueryTranslator... It is really meant for internal usage ;) how do I compile a query if methods are private ? :)

Thanks!

Daniel

All SQL for relationship navigation, that is, all SQL except for custom HQL/Criteria queries, is generated at startup and cached. You don't get any performance by isolating and externalizing this.

Well for one thing, the queries are all HQL, so they need to be interpreted. But that is not a big deal to me, what's more important is the time it takes for the machine to get up and running, the parsing of the xml files and preparation of the configuration...

Because at runtime the user is printing a report, I would prefer not to have to go through the initialization of the machine...

What do you suggest ?