Page History
...
- Aggregate create service: AQ_Aggregate_Create
- Aggregate read service: AQ_Aggregate_Read
- Aggregate update service: AQ_Aggregate_Update
- Aggregate delete service: AQ_Aggregate_Delete
| Note |
|---|
With the (deprecated) dossier manager it is possible to clear the profile with one service call (init). Persistency management functionality does not provide such a service, since such a service is not part of persistency management but instance management. |
Versioning
As shown in the aggregate list in the previous section, it is possible to specify versioning for aggregates. This means that when creating an aggregate, a version number is stored along with it. When updating an aggregate, it will result in an new entry with increased version number. When reading an aggregate, a specific version can be specified. This means that it is possible to load an older version of an aggregate into the profile. One can also decide to just alter the latest version without creating a new version. The same goes for deleting an aggregate, you can choose to delete an aggregate with all its versions, or only a specific version. It is advised to use a control entity to store the aggregate Ids as well as the version Ids.
...
Overview
Content Tools