[feat-2433]: record execution time for plugin subtasks#2455
Conversation
keon94
changed the title
keon94
changed the title
keon94
force-pushed
the
issues/2433
branch
3 times, most recently
from
b369053 to
bffe805
Compare
keon94
force-pushed
the
issues/2433
branch
3 times, most recently
from
2efcd5a to
51bf84a
Compare
|
Screenshot of the new subtasks table after a manual test
|
| "time" | ||
| ) | ||
|
|
||
| // Subtask_07112022 DB snapshot model of models.Subtask |
There was a problem hiding this comment.
@klesh is this still the correct way of managing migrations? I see recently there was a big refactor and everything is using init_schema.go now as opposed to individual migrations
There was a problem hiding this comment.
We added MultiConnection for all other plugins in v0.12. With this connection table added, every single table of the plugin was affected, as well as the Domain Layer tables, we have to flush the no-longer-valid data to maintain the data integrity, So, might as well drop existing migration scripts and rebuild the tables.
However, the Framework migration should be not affected, we should keep the migration scripts as it was, with that said, you are doing the right thing.
keon94
force-pushed
the
issues/2433
branch
3 times, most recently
from
3e31aa6 to
b0b7f46
Compare
keon94
force-pushed
the
issues/2433
branch
2 times, most recently
from
3a2cae2 to
3b61ec4
Compare
2 participants
label(bug, feature etc.)Summary
Does this close any open issues?
#2433
Screenshots
included below.
Other Information
Any other information that is important to this PR.