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 > > > > > > > > > > > If you reply to this email, your message will be added to the discussion > below: > http://openjpa.208410.n2.nabble.com/Null-field-not-persisted-for-Dates-tp5993519p5993586.html > To start a new topic under OpenJPA Users, email > [email protected] > To unsubscribe from OpenJPA Users, click here. -- View this message in context: http://openjpa.208410.n2.nabble.com/Null-field-not-persisted-for-Dates-tp5993519p5993590.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
