Read the rules before posting!
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.0

The question is the subj - should I be committing on every response? I've been following the caveat emptor example, and their Filter does "commit()", even though they never even use transactions....

I guess what my real question is - do I need transactions at all? If I don't use transactions, and just use session.updateOrSave(), will my objects be persisted? (that's not the case I've seen so far).

My problem with transactions is that what if I don't want the db connections to be made during the request itself... What if I'd rather use the cache for that moment, and do the rest later?

How can I do that? Transactions seem to force it, and not using transactions doesn't seem to persist it.

Thanks for any material in advance you guys, really appreciate it.

If you want to persist (save, update, delete) you MUST use transaction.
For plain reading (select) this is not necessary.
The connection won't be opened until absolutely necessary - if your data resides in cache --> no connection :-).

please search the forum,
you always need a transaction.

When you execute a simple select in JDBC, you have an underlying transaction started...

This is better if you always have this in mind.

No I understand that, but I noticed that whenever I do transaction.commit(), the server starts connecting to the database right away, and the user has to sit there and wait for it to happen, before they get a response page.

That's no big deal if I have a small commit, but what if I'm committing 10,000 statements or something? I want them to be sent to database later, and display the page to the user NOW.

How can that be accomplished?

see http://forum.hibernate.org/viewtopic.php?t=941328

try to explain better what you are doing, seems to me that 10,000 is a batch process, so look at
http://blog.hibernate.org/cgi-bin/blosx ... batch.html

every user should know about flush and flushMode...

hope this helps

Thanks for the doc. I guess I kind of came at a wrong angle about the batch processing.

Let's forget about that for a second.

Say, I simply want to add an.. "Item" to a database. If I do tx.commit(), this will cause the DB connection to be established right away, while the user sits and waits for the operation to finish.

Is it possible to add that item in such way, that it's cached, instead of being saved to the database right away, so the user gets quick response, and then it's persistsed later?

Asynchronous operation usually needs some kind of queue or messaging system. You might want to search on Google for this, it's not in the scope of Hibernate (it could be on top, of course).

Consider it for a future feature?

No! Thats what JMS products do.