Support update-if-changed style model update operations

[eclipse-viatra-bot]

| --- | --- | | Bugzilla Link | 470563 | | Status | NEW | | Importance | P3 normal | | Reported | Jun 19, 2015 04:55 EDT | | Modified | Oct 11, 2016 04:02 EDT | | Version | 0.7.0 | | Reporter | Zoltan Ujhelyi |

Description

If a model update operation does not change the model (e.g. setXXX is called with an old value), the operation is still executed, and possibly change notifications are sent.

It would be nice if we could update the model manipulation API to avoid these unnecessary notifications by checking whether a real change is necessary. Ideas for support:

1. Change existing methods to always check for changes.
2. Provide alternative API implementations to always check for changes.
3. Provide additional primitives that check for changes.

As model manipulation operations are executed many times, the comparison can be expensive, so I don't think, option 1. is a good contender. Option 2. does not require changes to transformation (only a different setup), but for efficient execution it might require code duplication; option 3. requires changes in transformations.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Mar 17, 2016 08:34

Updated 0.9 target milestones to 1.2

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Mar 17, 2016 08:47

Postponed tickets to 1.3

[eclipse-viatra-bot]

By Zoltan Ujhelyi on May 26, 2016 08:43

1.3 M1 already passed.

[eclipse-viatra-bot]

By Zoltan Ujhelyi on Jun 09, 2016 05:57

Postponed to 1.4