New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change schedule data on global scope edit #262

hsoft opened this Issue Jun 22, 2013 · 1 comment


None yet
1 participant

hsoft commented Jun 22, 2013

From email:

When changing 'All future occurrences' the Scheduled transaction doesn't change.
I would expect it to change and reflect what is currently happening without touching any older and/or reconciled occurrences of that transaction.

The problem is that global scope changes aren't necessarily made "from the start" and thus not all global changes should warrant a change to the schedule itself, but yeah, there should be a special case where globally changing the first spawn of a schedule changes the schedule itself.

@hsoft hsoft closed this Jun 22, 2013


This comment has been minimized.


hsoft commented Jun 22, 2013

(from [fb634ecb7d07]) [#262 state:fixed] Schedules are now updated by global changes when appropriate.

When a global change becomes the first spawn of a schedule, it replaces the ref txn of the schedule. This is to avoid the confusing situations where the schedule transaction would be different from all its spawns, and that changing a schedule would have no effect on its spawn (a new global change would be required).

Also, deleting the first spawn(s) of a schedule will make its start date move forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment