Bugfix 1173: Correctly apply sortedness checks when calling update with date_range argument #1238
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.
Closes #1173
Also:
UNKNOWN
for all non-timestamp indexed dataframes. Previously, this would be set toASCENDING/DESCENDING
for int/range indexes based on theDataFrame.is_monotonic_<in|de>creasing
of the input df, but this information was not used for anythingdict
fromNativeVersionStore.get_info
to include thesorted
keysorted
field to theSymbolDescription
class returned fromLibrary.get_info
update