Don't limit merging by mimetype.
ClosedPublic

Authored by knauss on Nov 27 2015, 4:12 PM.

Details

Summary

Flags are provided with a default mimetype of emails,
and we want to avoid creating email items if a flag of a
groupware item changed.

notes from randa:

  • Fix assert in ItemCreateJob, to allow no mimetype in case of merge and

-> you are talking about kdepimlibs/akonadi/job/itemcreatejob ? -> I see there no assert.

  • Allow merging for everything except for payloads

-> I do not understand

Diff Detail

Repository
R165 Akonadi
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
knauss updated this revision to Diff 1400.Nov 27 2015, 4:12 PM
knauss retitled this revision from to Don't limit merging by mimetype..
knauss updated this object.
knauss edited the test plan for this revision. (Show Details)
knauss added a reviewer: dvratil.
dvratil accepted this revision.Dec 28 2015, 1:13 PM
dvratil edited edge metadata.

Makes sense. It should not be possible to have multiple items with same RID in one collection, so removing the mimetype condition there does not make any change.

We already learned that GID-based merge is dangerous and can have conflicts, so weakening the constraint by removing the mimetype probably increases the chance of a conflict (it's possible to have multiple items with the same GID but different mime types in a single collections), but that's why we switched to RID merge and use GID only as a fallback .

This revision is now accepted and ready to land.Dec 28 2015, 1:13 PM
knauss abandoned this revision.Mar 15 2016, 4:19 PM
knauss edited edge metadata.
knauss set the repository for this revision to R165 Akonadi .
This revision was automatically updated to reflect the committed changes.