Can an object with uninitialized lazy collectsions (whose elements are a UserType) be saved without first loading the lazy collection. I have been told this can be done, but I can not get it to work. The code generally looks like this:



On the last line, when trying to saveOrUpdate(), Hibernate tries to load the lazy collection before saving. I just want it to update the one thing I changed... Can anyone give me some direction here? Any help is appreciated.

Thanks in advnace for all responses.

Not sure if this will solve your lazy loading problem, but...

If your Session is still open you don't need to call update (or saveOrUpdate). Either commit the transaction or flush the session (depending on you autocommit setting in the db) will save any changes you made to the object.

If like me you came to Hib' from an EJB 1.1 background you'd expect to have to call some sort of 'update' but Hib' takes care of that if the object is still associated with an open Session.

Cheers,

Nick

That is true. Although it still tries to load the lazy collections.

Any one have and *ideas* (they don't have to be spot on)? I'm really getting desperate here.

Most likely, you have cascade="save-update" or "all" enabled for this association. There is nothing "lazy" happening, it's just Hibernate looking for any modifications you might have made to the collection elements, because you told it to do so.

I can only repeat that saveOrUpdate() is probably not what you are looking for if you just want to have a SQL UPDATE with your changes. For this, just commit the Transaction (implicitely flushes the Session), close the Session.

When I first read this I thought, "Yes! That's probably it!", but cascade for the collection is set to "none". On update() Hibernate still calls the getter for my uninitialized lazy collection. I do want to use update because my transaction spans multiple method calls, and I only want to commit if everything succeeds?

Should the getter for my collection be called in this situation?

No, and your next step will be a Hibernate TRACE level log (don't post it here!) that will tell you why Hibernate would think it has to update the associated instances. If you have isolated the lines of log, post all that is mentioned in the red box.

Thanks for your responses.

I've been trying to get the logging going with the JDK 1.4 logging, but am failing so far. Can you tell me or point me to somewhere that demonstrates this? I found this: http://www.hibernate.org/119.html#A15 but it wasn't very helpful.

I tried both:
net.sf.hibernate=TRACE -- this gave an error, it doesn't like TRACE
net.sf.hibernate=FINEST

DEBUG will do