Jerry, I had the same problem, and now use <property name="openjpa.DetachState" value="loaded(DetachedStateField=true)"/>
I use DetachStrategy 'loaded' instead of 'fetch-groups' because fetch-groups gave me lots of problems. Please be aware that the entities should be Serializable and there are currently some problems with Externalizing if you use @Inheritance. See OPENJPA-1912 for more info [1]. LieGrue, strub [1] https://issues.apache.org/jira/browse/OPENJPA-1912 --- On Fri, 2/4/11, Rick Curtis <curti...@gmail.com> wrote: > From: Rick Curtis <curti...@gmail.com> > Subject: Re: Null field not persisted for Dates > To: users@openjpa.apache.org > Date: Friday, February 4, 2011, 6:55 PM > Jerry - > > That would be the problem then. We lost track of the fact > that you set this > field to null, and assume that it wasn't loaded. > Please review the > openjpa.DetachState [1] docs for more info. You could set > the property > listed below so that we will stream our > DetachedStateManager around. > > <property name="openjpa.DetachState" > value="fetch-groups(DetachedStateField=true)"/> > > [1] > http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_detach_graph > > Thanks, > Rick > > On Fri, Feb 4, 2011 at 12:49 PM, No1UNo <je...@jerrycarter.org> > wrote: > > > > > Yes, it is. The object is changed remotely and > then merged. The data on > > the wire is fine. > > > > On Feb 4, 2011, at 1:47 PM, Rick Curtis [via OpenJPA] > wrote: > > > > > Jerry - > > > > > > Is the Entity which you are trying to update > being > > serialized/deserialized? > > > > > > Thanks, > > > Rick > > > > > > On Fri, Feb 4, 2011 at 12:25 PM, Jerry Carter > <[hidden email]> wrote: > > > > > > > Using OpenJPA 2.0.1, I have a date field in > my entity. Setting the > > field > > > > to a non-null value causes the data to be > persisted as one would > > expect. > > > > Setting the value to null, however, > does not trigger an UPDATE > > operation. > > > > I'm still digging, but I'm sure that > someone else has encountered > > this. > > > > > > > > FWIW, the annotations for the field are > simple: > > > > > > > > @Temporal(TemporalType.DATE) > > > > @Column(name="purchase_date" private Date > purchaseDate; > > > > > > > > I do not specify 'nullable', but it defaults > to true and the field > > supports > > > > a NULL value in the database. > > > > > > > > -=- Jerry > > >