Chronos Gateway 0.4.2
A strict change is superseded by a commit to the database since its hold
- A strict change is superseded by a commit to the database since its hold, as the engine's strict proposals are. Its hold records
strict.target(the stamp of the world it merges into, from a preview of the merge) and every approval of it, through the API, a link or the cloud, merges bound to it: one approved after other changes reached the database is refused 409strict_targetand nothing is merged (reject it; the agent proposes again). A strict change is approved whole:only_tables/only_keyson one are refused 400.