FAIRSPC-68: fixed date filter for Jena #1524
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.
The bugfix found on a datamodel where we define some attributes as date fields. The whole application operates with datetime format (front-end with its Date type, back-end with Instant/timestamp for Postrgres) while in Jena we use date format. But all mappings for Jena map data type to date time. It wouldn't be an easy way to switch to pure date format everywhere (especially because we do not support data model evolution within data model versioning).
I suggest then just to add handling datetime for Jena in one place instead of reworking it in multiple places with un-answered question about how easily to deploy it to already existing environments with datetime formats.