On Fri, Aug 14, 2009 at 12:17 PM, Ravi P Palacherla (via Nabble) < ml-user+194843-327306...@n2.nabble.com<ml-user%2b194843-327306...@n2.nabble.com> > wrote:
> 2.2 Persistent Fields and Properties > If property-based access is used and lazy fetching is specified, portable > applications should not directly access the > entity state underlying the property methods of managed instances until > after it has been fetched by the persistence provider. Sure; I'm using field-based access, so this one doesn't apply. > 3.2.7.1 Merging Detached Entity State > The persistence provider must not merge fields marked LAZY that have not > been fetched: it must ignore such fields when merging. > Sure; this means that if I have an entity, E5, that has a lazy field to an E6 that has never been set, then if I merge E5 to E6, E5's null E6 reference shouldn't be used to wipe out any E6-related state that might exist on disk. That's not the issue here either. Thanks for dredging up these references, however. Best, Laird -- View this message in context: http://n2.nabble.com/insertable-updatable-%3D-false-question-tp3439111p3446109.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
