lorban wrote:
From the documentation, chapter 17.4:
Quote:
You can see the expected order by enabling debug logging for the org.hiberante.persister.entity level. With this level enabled Hibernate will print out the static SQL that is used to create, update, delete etc. entities. To see the expected sequence, remember to not include your custom SQL in the mapping files as that will override the Hibernate generated static sql.
See:
http://www.hibernate.org/hib_docs/v3/re ... erysql-cud
Yes, very true. The debug mode is where i got the correct SQL sequence of column. I am acutally looking for a help to understand how the column sequnce is generated by Hibernate while preparing(binding parameters) the statement. The idea is that you can not every time go into debug mode and see what is the sql generated and then prepare your query accordingly.
Lorban, it would be helpful if you could suggest the binding sequence of hibernate query.
Thanks