Use latest data timestamp for DB timestamp #251
Jump to bottom
8000
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>
willmurphyscode
approved these changes
Mar 7, 2024
willmurphyscode
pushed a commit
that referenced
this pull request
Mar 27, 2024
Bumps [xsdata](https://github.com/tefra/xsdata) from 23.6 to 23.7. - [Release notes](https://github.com/tefra/xsdata/releases) - [Changelog](https://github.com/tefra/xsdata/blob/main/CHANGES.rst) - [Commits](tefra/xsdata@v23.6...v23.7) --- updated-dependencies: - dependency-name: xsdata dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Today the DB timestamp is the oldest provider data timestamp, not the timestamp of when the DB was built. This reverses the semantics such that the latest data timestamp is used. This is helpful in scenarios when the cadence of DBs delivered is relatively high and the policy for failing providers is permissive. That means you can build many DBs with the same timestamp, which is not useful.