DM-47789: Convert to the Safir pagination support #1168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the new paginated query support in Safir, which was based on the original Gafaelfawr code but made more generic. This requires adding a new type for token change history entries that include the database row ID (required to use the pagination cursor) and moving enums used in the database schema into a separate module since the history models module now needs to import symbols from the schema.
Delete the Gafaelfawr `LinkData` model in favor of `PaginationLinkData` from Safir. This is the same model with some minor tweaks and a different name.
Now that the pagination code in Safir is used, `InvalidCursorError` was never raised and can be safely deleted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use the new paginated query support in Safir, which was based on the original Gafaelfawr code but made more generic. This requires adding a new type for token change history entries that include the database row ID (required to use the pagination cursor) and moving enums used in the database schema into a separate module since the history models module now needs to import symbols from the schema.