This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Feature/117 ftrack mongo id custom attribute #118
Merged
+272
−207
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.
Avoid Mongo ID custom attribute per each entity type. Instead of that is custom attribute hierarchical.
To apply this is required to launch
Create/Update Custom Attribute
action:1.) will create hierarchical attribute for Avalon Mongo ID
2.) transfer values for each previous custom attributes (per entity type)
3.) previous custom attributes are deleted if transfer was successfully completed
This process is for whole ftrack server and it's not possible to do rollback!!! (use wise).
It is possible to recreate previous custom attributes with develop branch and running
Create/Update Custom Attribute
but IDs won't be filled (run sync to avalon to fill them).This is NOT required step in production (may take a few minutes to do so) but is automatically done when
Create/Update Custom Attribute
action is triggered.Hierarchical custom attributes are queried from
ContextCustomAttributeValue
table instead ofCustomAttributeValue
to achieve better stability.