Cheers,
john
> -Ursprüngliche Nachricht-
> Von: Marc Logemann [mailto:l...@logemann.org]
> Gesendet: Freitag, 24. August 2012 11:55
> An: users@openjpa.apache.org
> Betreff: Re: update null relation on merge()
>
> i have not configured a detachState somewhere, so i guess its
>> Von: Marc Logemann [mailto:l...@logemann.org]
>> Gesendet: Freitag, 24. August 2012 11:43
>> An: users@openjpa.apache.org
>> Betreff: Re: update null relation on merge()
>>
>> 1:1 relations are eager by default And eager could be
>> only a loading iss
Which detached state are you using?
> -Ursprüngliche Nachricht-
> Von: Marc Logemann [mailto:l...@logemann.org]
> Gesendet: Freitag, 24. August 2012 11:43
> An: users@openjpa.apache.org
> Betreff: Re: update null relation on merge()
>
> 1:1 relations are eager by
one solution is to set the FetchType to EAGER for the
> Relationship.
>
> Cheers,
>
> John
>
>> -Ursprüngliche Nachricht-
>> Von: Marc Logemann [mailto:m...@logemann.org]
>> Gesendet: Freitag, 24. August 2012 11:17
>> An: users@openjpa.apa
Betreff: update null relation on merge()
>
> Hi,
>
> i am facing something like described here:
>
> http://openjpa.208410.n2.nabble.com/null-values-not-updating-t
> d3224059.html
>
> We get a JSON graph from frontend, let Spring deserialize it
> to a java object (wit
Hi,
i am facing something like described here:
http://openjpa.208410.n2.nabble.com/null-values-not-updating-td3224059.html
We get a JSON graph from frontend, let Spring deserialize it to a java object
(with OID set) and want to change the existing object in the db. This works for
simple attrib