Workflow steps history database about workflow-core HOT 4 CLOSED

This info is currently stored in the ExecutionPointer, of which each workflow instance has an array that is persisted to the chosen provider. In MongoDB, it's quite easy to see, but currently, if you are using one of the relational DB providers, these are serialized as a json string to a varchar field. I am in 2 minds about splitting them out into a separate table, perhaps you could help me decide ;)

from workflow-core.

I think that the main benefit of creating a new Db table that stores Step instances is the ability to store user definable information per Step as it is triggered.

from workflow-core.

So, I have added an ExtensionAttributes field on the ExecutionPointer class, and if you look at WorkflowCore.Users, you can see an example of a decoupled extension package making use of this. I would like to split the execution pointers out into a separate table for the relational DB providers, but this will be a breaking change, no migration for existing databases. Given that this project in only 2 months old, we should probably do this sooner rather than later.

from workflow-core.

Actually, we could provide a migration for existing databases, I'm just not sure it is worth it given how new the project is. Thoughts?

from workflow-core.