fix(db) run select transformations before process auto fields #9049
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.
Summary
Run select transformations before process auto fields.
Background: there has been reports that for example EE keyring may not work well with vaults. It might be due to fact that for some reason the read transformations ran after
process auto fields
. I think the correct place to run transformations is to run them late as possible with writes and early as possible with reads. I will open this on EE too, so I can get an idea if this order change causes any problems there.