Hi,

I'm using <sql-query/> within hibernate mapping files to represent sql statements. I have below qns regarding <sql-query/> -

1) Does hibernate parse the sql and keep it in precompiled statement format?

2) Do I have to include key fields within the sql statement specified inside <sql-query/> element? If I dont, hibernate throws an exception of Column not found.

3) Why is it mandatory to use Instrument ANT task onto value objects while using <sql-query/>? Is there any workaround for that?

Could someone plz give me any pointers for this qns? Thanks in advance for your help!

#1 we always use prepared statements, but the sql-query is not directly cache by hibernate

#2 yes, otherwise how should hibernate be able to see what the id is of your object ? (you can in H3 use scalar queries which doesnt have this requirement, but then cant return user objects)

#3 Have no idea why you should need to run the instrument ant task, how did you get that idea ?

/max

Max,

Thanks for your reply !!

#1 we always use prepared statements, but the sql-query is not directly cache by hibernate

----- Does that mean <query/> is more performance optimized than <sql-query/>?

#2 yes, otherwise how should hibernate be able to see what the id is of your object ? (you can in H3 use scalar queries which doesnt have this requirement, but then cant return user objects)

----- That sounds good. I dont have problem selecting id fields. Just wanted to confirm if thats the right direction.

#3 Have no idea why you should need to run the instrument ant task, how did you get that idea ?

----- This is for handling lazy properties. I read abt Instrument task at

http://www.hibernate.org/hib_docs/v3/re ... properties
http://jira.jboss.com/jira/browse/EJBTHREE-217

In some senses the <query> is better cached and optimized than <sql-query> but do a performance measure before you deem it slow ;)

Lazy properties has nothing to do with sql-query.

/max