You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though the testing of this issue is not working on 5.0.0 (see #434), the behavior we've seen on 4.9.1 is misleading when it comes to "datetime" filters. Here is why:
If you have a datetime filter Created At, it will ask you only for date. You select 21.02.2023. Your data is having random datetimes like 21.02.2023 10:35:23 ... (with time)
The condition applied in BE is 21.02.2023 00:00:00 == 21.02.2023 10:35:23 which is false. So basically using a datetime filter with value (not interval) is pointless since it will only target entries with time 00:00:00.
Shouldn't time be part of the filter, or when selecting a day, it should cover the whole 24h interval (00:00:00 -> 23:59:59)?
The text was updated successfully, but these errors were encountered:
This is a minor bug.
Prerequisites
(enso is made of many specialized packages: https://github.com/laravel-enso)
Description
Even though the testing of this issue is not working on 5.0.0 (see #434), the behavior we've seen on 4.9.1 is misleading when it comes to "datetime" filters. Here is why:
If you have a
datetime
filterCreated At
, it will ask you only fordate
. You select 21.02.2023. Your data is having random datetimes like 21.02.2023 10:35:23 ... (with time)The condition applied in BE is
21.02.2023 00:00:00 == 21.02.2023 10:35:23
which is false. So basically using adatetime
filter withvalue
(notinterval
) is pointless since it will only target entries with time 00:00:00.Shouldn't time be part of the filter, or when selecting a day, it should cover the whole 24h interval (00:00:00 -> 23:59:59)?
The text was updated successfully, but these errors were encountered: