Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Initial Version and Version 9 of Ticket #346


Ignore:
Timestamp:
09/27/2006 09:41:53 AM (15 years ago)
Author:
jmoore
Comment:

So, this has nothing to do with cascading. It actually is a mirkier question of the specification of "merge()". What's happening is thus:

  • Object A (detached on client) has field B set to C.
  • Field B, however, is immutable and won't be set in SQL or dirty detection. (i.e. no errors)
  • Session.merge(), however, copies all values from detached A to persistent A, which gets returned to user.

Working on a workaround.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #346

    • Property Cc callan added
    • Property Keywords hibernate merge iteration6 added
    • Property Summary changed from Passing non-proxied one-to-manys to server can return empty (non-null) collection to Merge needlessly/dangerously copies immutable fields.
  • Ticket #346 – Description

    initial v9  
     1Was: Passing non-proxied one-to-manys to server can return empty (non-null) collection ('''See comments below''') 
     2 
    13Several model objects have methods for adding items to collection-valued fields: 
    24{{{ 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.12977 sec.)

We're Hiring!