Hi,

I have read a few posts where people have discussed the need to use JDBC to do mutiple inserts/updates and deletes within the same session. Has anyone done benchmarks on the threshold (i.e. number of transactions) where JDBC becomes more condusive than using a Hibernate session? I have a few administrative screens in my application where permissions are assigned to userGroups, products are assigned to different catalogs etc, where the number of inserts/updates and deletes at any time would be less than 100 transactions. In such cases I am inclined to go with using a Hibernate session. Has anyone faced problems with doing this in the past?

TIA

The question you request is too vague. Hibernate use JDBC.