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.
- Timestamp:
-
09/27/06 09:41:53 (18 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
-
- 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.
-
|
initial
|
v9
|
|
| | 1 | Was: Passing non-proxied one-to-manys to server can return empty (non-null) collection ('''See comments below''') |
| | 2 | |
| 1 | 3 | Several model objects have methods for adding items to collection-valued fields: |
| 2 | 4 | {{{ |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.13241 sec.)
