PK_PMARK_ask_entities

PK_ERROR_code_t                  PK_PMARK_ask_entities
(
--- received arguments ---
PK_PMARK_t                       pmark,         --- destination pmark
const PK_PMARK_ask_entities_o_t *options,       --- options structure

--- returned arguments ---
int                       *const n_new,         --- number of entities created
int                      **const new_entities,  --- entities created
int                       *const n_mod,         --- number of entities modified
int                      **const mod_entities,  --- entities modified
int                       *const n_del,         --- number of entities deleted
int                      **const del_entities   --- entities deleted
)


This function returns the entities that would be created, modified and deleted
if rolling to the destination 'pmark'.


Specific Errors:
    PK_ERROR_rollback_not_started   (MILD) Partitioned rollback is not active
    PK_ERROR_bad_mark               (MILD) Bad partition mark to roll from
    PK_ERROR_frustrum_failure       (MILD) The frustrum returned an error


The behaviour is the same as PK_PMARK_goto_2, except that the modeller state is
not changed.  If the option 'from_pmark' is used to specify a pmark then the
behaviour is as though the partition were initially rolled to that pmark. In
this case, the pmarks must be in the same partition.

This function should only be called when partitioned rollback has been started
by calling PK_DELTA_register_callbacks.

Further rollback tracking controls can be specified in 'options'.

The 'mod_entities' list is generated using internal data structure changes.  It
is not recommended for this list to be used in application tracking for the
following reasons:

    o Some changes (as perceived by the application) may not be present in the
      list.
    o Although all changed attributes ARE included in the list, some additional
      entries may also be present.