fix: revert assertions tuple key order change #1217
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.
Description
In v1.3.8, we introduced a change where that reordered fields on a tuple from object, relation, user to
user, relation, object
. Since assertions are currently stored as a marshaled binary in both Postgres and Mysql storage adapters, this meant that any assertion written before v1.3.8 would result in being read in an incorrect order.For example, a request to write assertions:
would be read back as
Important: any assertion written after running v1.3.8 will present the same problem after the changes in this pull request are merged.
References
openfga/api#123
Review Checklist
main