Im in hibernate 3, and have a general question. If this is in the docs, kindly point me to which one.

This is my understanding of how hibernate works (in pseudocode):

1. retrieve an object
2. edit the object
3. insert an object into the session
4. close and commit

Both objects will get persisted to the DB (the one that was retrieved and edited, and the one that was explicitly inserted).

This is how I am considering going (since I want to reduce the magic happening to make DB stores explicit).

In the same 4 steps above, only the inserted object gets persisted. To get both to be persisted, you do this:

1. retrieve an object
2. edit the object
3. insert an object into the session
4. store the retrieved and edited object
5. close and commit

So basically all retrieved objects are detached by default. And I realize this kills any caching. Thats ok. Is there a setting to do this be default or do I need to detach after retrieving each one?

Thanks,
Chris

If you don't close the session before editing the object, then there is no setting that I am aware of. I believe you will need to dissociate it from the session. Look at session.evict(object).

I have to admit, though, I don't understand why you would want to do this in the first place...

5. commit Tx THEN close Session

I still have the problem of auto flush sending statements to the DB. I dont want autoflush off (I think, since do all update/store/inserts flush?), I just want the objects detached automatically.

Thanks,
Chris

Query.setReadOnly(true)

I need to revoke my helpful rating, I should have tried this before rating. :) JK. Seriously though I used this, and when reattaching to the session it will not let me, per my example above? I tried to store() to the same session and it ignored them. This is definitely not what I am looking for, and I do not really see why it works like that. Oh well, agree to disagree. I will just manually detach each object selected in my Hibernate-wrapper framework unless there is another suggestion... Thanks, Chris

btw, it would be nice to not have to make a dirty checking listener, just a global param that says "do not dirty check"

Interceptor.findDirty()