Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: update null relation on merge()
From: Marc Logemann <li@logemann.org>
In-Reply-To: 
 <88CB62524DE0644AAE21D8BAB8CFC0CA01B03A8F@dueexs06.bertschi.domain>
Date: Fri, 24 Aug 2012 11:55:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6460A01-6E4D-4682-B2E5-FAE1DC319714@logemann.org>
References: <1414D4DD-AB3F-4CA9-8888-7005261FD0EC@logemann.org>
 <88CB62524DE0644AAE21D8BAB8CFC0CA01B03A47@dueexs06.bertschi.domain>
 <6A952FC2-CEED-4945-85B3-EF5D4EC3020E@logemann.org>
 <88CB62524DE0644AAE21D8BAB8CFC0CA01B03A8F@dueexs06.bertschi.domain>
To: users@openjpa.apache.org

i have not configured a detachState somewhere, so i guess its the =
default...

---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de


Am 24.08.2012 um 11:50 schrieb Boblitz John <John.Boblitz@BERTSCHI.com>:

> Which detached state are you using?
>=20
>> -----Urspr=FCngliche Nachricht-----
>> Von: Marc Logemann [mailto:li@logemann.org]=20
>> Gesendet: Freitag, 24. August 2012 11:43
>> An: users@openjpa.apache.org
>> Betreff: Re: update null relation on merge()
>>=20
>> 1:1 relations are eager by default.... And eager could be=20
>> only a loading issue. I have a "merge" issue here.
>>=20
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>=20
>>=20
>>=20
>>=20
>> Am 24.08.2012 um 11:28 schrieb Boblitz John=20
>> <John.Boblitz@BERTSCHI.com>:
>>=20
>>> Good Morning,
>>>=20
>>> I had this often and one solution is to set the FetchType=20
>> to EAGER for=20
>>> the Relationship.
>>>=20
>>> Cheers,
>>>=20
>>> John
>>>=20
>>>> -----Urspr=FCngliche Nachricht-----
>>>> Von: Marc Logemann [mailto:ml@logemann.org]
>>>> Gesendet: Freitag, 24. August 2012 11:17
>>>> An: users@openjpa.apache.org
>>>> Betreff: update null relation on merge()
>>>>=20
>>>> Hi,
>>>>=20
>>>> i am facing something like described here:
>>>>=20
>>>> http://openjpa.208410.n2.nabble.com/null-values-not-updating-t
>>>> d3224059.html
>>>>=20
>>>> We get a JSON graph from frontend, let Spring deserialize it to a=20=

>>>> java object (with OID set) and want to change the existing=20
>> object in=20
>>>> the db. This works for simple attribtues likes Strings and=20
>> so but not=20
>>>> for 1:1 relations. If we set it to "null" in the frontend,=20
>> we want to=20
>>>> change the 1:1 relation to null. Instead it leaves the 1:1=20
>> relations=20
>>>> untouched with the old object reference in it.
>>>>=20
>>>> The OpenJPA docs once said: "When attaching null fields in these=20
>>>> cases, OpenJPA cannot distinguish between a field that was=20
>> unloaded=20
>>>> and one that was intentionally set to null. In this case, OpenJPA=20=

>>>> will use the current detach state setting to determine how=20
>> to handle=20
>>>> null fields: fields that would have been included in the detached=20=

>>>> state are treated as loaded, and will in turn set the=20
>> corresponding=20
>>>> attached field to null."
>>>>=20
>>>> At this point i dont know what to do. Spring knows its detached=20
>>>> because we submit our @Id Field =3D> OID with a valid and existant=20=

>>>> value but the merge itself just ignores null values for=20
>> 1:1 relations=20
>>>> and leaves them as they were. Is there any sensible way to tell=20
>>>> OpenJPA to merge "null"
>>>> relations differently?
>>>>=20
>>>> ---
>>>> regards
>>>> Marc Logemann
>>>> http://www.logemann.org
>>>> http://www.logentis.de
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20