Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:
3.2

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

MySql

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:


Problems with Session and transaction handling?

Read this: http://hibernate.org/42.html


Hello, I use the 2-session-pattern for a RCP application, thats mean I use a session per application only to read data and the second one to write. I read that I must make the read-session read-only. How I can do this?

See this: http://www.docjar.com/docs/api/org/hibe ... %20boolean)

=> Session.setReadOnly(Entity, boolean)

ok I know setReadOnly I have think its exists a method to set the session one time readOnly in the creation, independent from a entity...

I don't think this method exists.

Another way to do it could be putting the transaction in readonly mode, instead of the session. But no standard hibernate method let you do it. For my case, I do it in the tx demarcation xml file(the declaration of my tx proxy).

Maybe also see Query.setReadOnly(boolean), every queries in this mode will retrieve entities in readonly mode.

Read-only transactions are _not_ the same as session.setReadOnly() or query.setReadOnly(). The first is a hint for weak DBMS implementations that you only want to do SELECTs - a good DBMS transaction system should figure this out automatically. The latter is a setting that disables object snapshots at the Hibernate persistence context level. That means no dirty checking of these instances during flush-time. You safe memory but you still get the repeatable read guarantees of the persistence context cache.

But I read in the Best Practices for Thick-Client Applications (i.e., non-web apps.) http://www.hibernate.org/333.html that when we use a think client application the best method is to use a multi session pattern...


"...- One session will be read-only and allows the user to browse around in the application's data.

- Then for each Commands (or major delineated Task) I would create a separate session and transaction...."

What is the best method to implement this. I use criterias and queries, that means i get a list of entities. must i itereate them and set readonly?

The reason is that i want more performence when i load the entities.[/url]

I didn't write that page and I don't think this is a good approach either. Read my blog entry that is linked on top of that page.