Support second-level precision on searches against DateIndex#81
Merged
ramonski merged 17 commits intosenaite:2.xfrom Mar 13, 2026
Merged
Support second-level precision on searches against DateIndex#81ramonski merged 17 commits intosenaite:2.xfrom
ramonski merged 17 commits intosenaite:2.xfrom
Conversation
Contributor
Author
|
@xispa after checking the changes I noticed that the catalog date filter is missing in this commit:7051e5d...861ae75. |
…-fix-filter-timestamp
xispa
changed the title
ramonski
approved these changes
Mar 13, 2026
Contributor
ramonski
left a comment
ramonski
left a comment
There was a problem hiding this comment.
Great, thanks!
Works as expected for our use case.
It's a pity that the DateIndex has this 1 minute constraint.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 of the issue/feature this PR addresses
This PR fixes timestamp filtering for API queries using created_since and modified_since fields. It ensures results are filtered with full second precision
Current behavior before PR
API queries with
created_sinceormodified_sincecould return records with timestamps before the specified thresholdDesired behavior after PR is merged
API queries now filter records by the exact timestamp
--
I confirm I have tested the PR thoroughly and coded it according to PEP8
standards.