Hi,

Is there a way to specify that only non-null fields should be written to the DB on an update?

Thanks!

Nevermind, I just noticed the dynamic-update attribute. That fixed it up.

Well, for some reason, the dynamic-update is no longer having any effect (maybe it never was in the first place and I am just going nuts? :) ).

Take this simple example:



Persisting this from an XML such as this:



causes the "bar" field to be updated, despite my dynamic-update setting.

What gives?!?

:(

(I am constructing a dialogue with myself in here, but oh well) ... so I guess the issue here is that the dynamic-update will update only those fields that have changed. That is not exactly what I want -- what I want is a way to update only those fields that are non-null.

Is there a way to do this with the mappings? Or do I have to introduce something programmatic?

Thanks.

OK ... so more elaboration on this topic:

it seems like it would make sense for there to be an option that allows a detached object with an existing ID to be merged into the session as an update, but only updating non-null values.

I can imagine a number of scenarios where a small delta change is made, and only that delta is sent to the receiving application that holds the Hibernate session ... from there, it would be really nice to be able to do an update against only those fields that differ and are non-null.