Details
-
Sub-task
-
Resolution: Unresolved
-
Major
-
None
-
2.0.1
-
None
-
Medium
-
Description
Custom mapping, especially dynamic custom mapping is very difficult to use because objects are not migrated automatically when a class is changed.
I propose the saving of the document where customMapping has changed for it's BaseClass should trigger the load of all objects of that class, then the deletion of all those objects, then the save of the class, then the save of all the objects. Some kind of failsafe should also be put in place to prevent the wiping of all the objects in the event of bad custom mapping.
It should be able to support:
- Change from standard form to dynamic custom mapping.
- Change from dynamic custom mapping to standard form.
- Alteration of dynamic custom map.
- Change from standard form to internal custom mapping.
- Change from internal custom mapping to standard.
Is it possible to detect changes in internal custom mapping?
In the event of an error, all objects should be saved in standard form.