sql: add support for workflow retry params #1460
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note to Reviewer:
The 'executions' table at this point has close to 50 columns. We could consider storing the mutable state as a blob in MySQL - however the pros/cons of doing so are not very clear at this time. So, I have decided to tackle this problem independently after getting some data on the performance implications of such a change.
Pros/Cons to having too many columns are below. The I/O cost is likely to be the same with both blob and wide rows
Cons
Pros