Eclipse Community Forums: EclipseLink » Changing lazy attributes when shared cache disabled

Help

Home

Home » Eclipse Projects » EclipseLink » Changing lazy attributes when shared cache disabled

Show: Today's Messages :: Show Polls :: Message Navigator

Changing lazy attributes when shared cache disabled [message #1252185]

Fri, 21 February 2014 01:38

Peter Nehrer

Messages: 241
Registered: July 2009

Senior Member

Hi,

I observe the following behavior when I disable shared cache via <property name="eclipselink.cache.shared.default" value="false"/>:

1. start transaction
2. fetch existing object
3. change eager property
4. change lazy (lob) property
5. change another eager property
6. commit and close

The change in #3 gets lost -- the field doesn't even show up in the UPDATE statement.

With shared cache enabled, that is not the case.

Is this expected or a bug? Refreshing the object or locking it beforehand doesn't seem to help. Am I expected to ensure all lazy attributes that I intend to modify are loaded up-front? I can do that; it just seems odd.

Thanks in advance for any insight.

Report message to a moderator

Re: Changing lazy attributes when shared cache disabled [message #1256850 is a reply to message #1252185]

Tue, 25 February 2014 21:45

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

If this is all happening in the same EntityManager context, on the same managed entity, it is unexpected and seems like fetching the lazy attribute might be forcing a refresh to occur. Check the state of the property changed in step 2 within the entity before and after step 3 to see if it is changed by trenching the lazy attribute or if something else might be happening.

Report message to a moderator

Previous Topic:	Reload Persistence Unit at Runtime
Next Topic:	JPQL count query slow

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 12:57:41 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter