|Changing lazy attributes when shared cache disabled [message #1252185]
||Thu, 20 February 2014 20:38
| Peter Nehrer
Registered: July 2009
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.
Powered by FUDForum
. Page generated in 0.01733 seconds