You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the updateLevel flag at relationalBones, it might be useful to provide generally a generic way to mark entities as "too old to be updated" at some point, so these entries won't be updated by the updateRelations task.
Following use-case: There is an database entry representing a task. The task's relationalBones should be updated all the time when something changes. At some point, the task is marked as "completed". And 1 year later, nobody will every take a view into this task again - so its relationalBones are not worth to be kept updated. Therefore, the entry is marked as "archived" or some kind, and updateRelations won't match it anymore.
The text was updated successfully, but these errors were encountered:
Not sure how we could implement this in a sane way. Either we'd have to create a deferred/periodic task that checks for these entries and the actively rewriting its viur-relations objects when expired - or have them sit indefinitely as active and update them once more after they expired (whenever that may happen). If no-one will take a look anyway - can't you just delete all tasks older than 6 Month or so?
Similar to the updateLevel flag at relationalBones, it might be useful to provide generally a generic way to mark entities as "too old to be updated" at some point, so these entries won't be updated by the updateRelations task.
Following use-case: There is an database entry representing a task. The task's relationalBones should be updated all the time when something changes. At some point, the task is marked as "completed". And 1 year later, nobody will every take a view into this task again - so its relationalBones are not worth to be kept updated. Therefore, the entry is marked as "archived" or some kind, and updateRelations won't match it anymore.
The text was updated successfully, but these errors were encountered: