|
If you were logged in you would be able to see more operations.
|
|
|
db4o Core
Created: 20/Apr/10 01:55 PM
Updated: 03/May/10 02:54 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
7.13.143
|
| Fix Version/s: |
8.0.145
|
|
|
Issue Links:
|
Related
|
|
This issue is related to:
|
|
COR-1294
Optimize collection storage to avoid unnecessary updates when TP is enabled.
|
|
|
|
|
|
|
|
|
For a (global or class specific) configured update depth > 1 (in particular collections), activated - but unmodified - child elements will be updated.
// all classes involved (Holder, Item, Collection) implement Activatable
Holder holder = retrieveOnlyInstance(Holder.class);
holder.collection().get(0).id()); // activate
holder.collection().add(new Item(43)); // modify collection structure
db.commit(); // activated item will be updated in db
see ActivatableListUpdateTestCase in staging
Potential solution: The TP aware update depth could carry a reference to the modified set along with the tp commit mode and could skip updating Activatable objects that are not listed as modified.
|
|
Description
|
For a (global or class specific) configured update depth > 1 (in particular collections), activated - but unmodified - child elements will be updated.
// all classes involved (Holder, Item, Collection) implement Activatable
Holder holder = retrieveOnlyInstance(Holder.class);
holder.collection().get(0).id()); // activate
holder.collection().add(new Item(43)); // modify collection structure
db.commit(); // activated item will be updated in db
see ActivatableListUpdateTestCase in staging
Potential solution: The TP aware update depth could carry a reference to the modified set along with the tp commit mode and could skip updating Activatable objects that are not listed as modified.
|
Show » |
| There are no comments yet on this issue.
|
|
Improvement
Resolved
