Hi All,

I wrote a small app that fetches a bunch of records from the db, processes each one and then saves it in the db.

a transaction is opened before the fetch, committed after the first object is processed and then new transactions are created and committed for each object.

What i see happening is that only the first entity is saved to the DB , the following ones are not saved.

If i commit all objects at once it works, or if i do a new fetch within each transaction, but not one fetch and multiple commits.

IS this behaviour by design?
how can I change it?
is it possible to at least know if the entity is not in the right state and wont persist?

Thanks,
Shay

Post code.

code is pretty complex and cropping to a small size is a bit tricky.

I guess the main question is what happnes to entities that have been fetched as part of a transaction, which is now closed. should they still be valid?

since hibernate doesnt have nested transactions, how do objects behave when they are part of multiple transactions.

Shay

The are valid, of course. Just lazy fetched parts may malfunction.



Hibernate is not a transaction manager. It is up to you to control your transactions. But, basically, detached object does not care about transactions. They are simple JavaBeans in the same way as your own constructed JavaBeans would be.

That why I think your code contains some obvious error. I do not think transactions are to blame.

does a commit detach an object?

how can i tell if an object is detached or not?

Whats the best way to re-attach?

thanks,
Shay

No.



Not sure. Try "Session.get()".



A lot of ways to do that. For example use "Session.saveOrUpdate()", or "save", or "persist", or "merge", or read the manual :)