Handle primary key updates in the synchronisation library

Issue #12 wontfix
Pierre-Marie de Rodat
created an issue

The synchronisation library should handle updates that modify an entity’s primary key. This should requires to change the format of updates to specify the old and the new primary key (currently, an update contains only a single dictionnary of all up-to-date fields).

Comments (1)

  1. Antoine Pietri

    A primary key shouldn't be updated. We could use unique IDs as primary keys instead of having a special case for primary keys update (which could interact badly with other services such as redmine).

  2. Log in to comment