Is opening a transaction necessary for select?

cagan327 · **Posted:** Fri Jul 30, 2004 2:31 am

Is it necessary to create a new transaction for select queries like

Code:

MyClass entity = (MyClass) session.get(MyClass.class, id)

as commit and/or rollback does not make sense in this context...

Thanks,
Cagan

borak · **Posted:** Fri Jul 30, 2004 4:22 am

borak · **Posted:** Fri Jul 30, 2004 4:22 am

michael · **Posted:** Fri Jul 30, 2004 4:44 am

Yes! Always do explicit transaction management! This has been discussed numerous times alredy in the forum.

cagan327 · **Posted:** Fri Jul 30, 2004 12:02 pm

In case of an HibernateException during the select with tx management, are tx.commit and tx.rollback necessary?

so is it:

Code:

try{
   session  = get current session
   tx = session.beginTransaction()
    return (MyObject) session.get(MyObject.class, id);
}catch(HibernateException) he){
...
}finally{
    close the session
}

or

Code:

try{
   session  = get current session
   tx = session.beginTransaction()
   MyObject obj = (MyObject)session.get(MYObject.class, id);
   tx.commit();
   return obj;
}catch(HibernateException) he){
  try{
     tx.rollback();
  }catch(HibernateException he){
  }
}finally{
    close the session
}

christian · **Posted:** Fri Jul 30, 2004 12:04 pm

Why shouldn't they be required?[/url]

michael · **Posted:** Fri Jul 30, 2004 12:04 pm

I think it is good style to do transaction handling just like in every other case. Commit if everything is fine, rollback if there is an exception.

bertrand · **Posted:** Mon Aug 02, 2004 9:15 am

Yes!

Besides all other reasons already mentionned in the thread (and others), one can add the following:

If not protected by a transaction you may be impacted by changes performed by other threads (cfr. transaction isolation level). Think about it...

cagan327 · **Posted:** Mon Aug 02, 2004 6:52 pm

Got the point..Thanks.