Closed (works as designed)
Project:
Drupal core
Version:
10.1.x-dev
Component:
views.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Apr 2019 at 20:36 UTC
Updated:
22 Feb 2023 at 09:35 UTC
Jump to comment: Most recent

Comments
Comment #2
mandclu commentedComment #3
w01f commentedPerhaps the smart date module has a better implementation for performance for the date range feature - that could possibly, eventually, be used as the default in core?
https://www.drupal.org/project/smart_date
Comment #4
w01f commentedHi, after reviewing several related issues and coming to at least a better understanding of this and related issues, I've made a new issue in drupal core about this - https://www.drupal.org/project/coredev/issues/3063377#comment-13156172
Please feel free to comment, add, or correct any of the information I've put together!
Comment #5
mandclu commentedComment #6
lendudeThanks for raising this!
Can we get numbers on this? I'm sure it's true, it's just that numbers give credibility to the statement.
Some sort of semblance of a possible direction of a fix for this might be nice too (what SHOULD the query look like to be more performant but so it still works with the existing database structure and across different database backends). Now it just reads like an observation. The issue here #3063377: Dates and dateranges - core handling, storage, and planning for the future (not sure why an issue there is needed/wanted, that is a pretty dead project it seems), talks about the difficulty of working with dates stored as strings. If that is indeed the underlying difficulty here, that seems like an issue that needs to be fixed somewhere else then Views.
Comment #7
w01f commentedHi @Lendude, I've added a short clarification of the purpose of the issue you linked. Here's the excerpt:
Comment #13
amber himes matzThanks for reporting this issue. We rely on issue reports like this one to resolve bugs and improve Drupal core.
As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" back in June 2019.
There has been no activity here for 3 years and 11 months.
Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after 3 months.
Thanks!
Comment #16
quietone commentedAs stated in #13 more information is needed here. Since that has not been supplied in 4 years I am closing this issue.
If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide the information asked for in #6.
Thanks