capturetime strangeness within year

[carlseibert]

Hi,  I just stumbled on some odd capturetime behavior.

If I have an image made on, say, 4-5-2019 and I include a time delimiter in a search for that picture, like so "some subject capturetime > 1-1-2019", the picture won't return. Same happens in the other direction. "< 12-1-2019" will also fail.

But if I do greater than or less than some specific day in a different year, like "> 1-1-2018", it works properly. The problem seems to affect relative searches that use specific dates within the year of the capture time. "=2019" will work properly, as will "> 2012".

I tried some different relative times formats like "< 6 months ago". That one worked with a bunch of different values.  I tried different years to see if 2019 was just jinxed and it wasn't. (2020, yeah. Probably. But 2019 was OK ;-) But "between" searches would work with years, but fail with specific dates or months. "Between 2020 and 2021" worked for a picture from 1-7-2021. "Between 1-1-2021 and 2-1-2021" failed. As did "between 1-2019 and 2-2022" The "between" searches didn't like specific dates even if they were from different years.

A bug, perhaps?

-Carl

 

[Kirk Baker]

Carl,

Dates need to be in one of the following formats:

4 digit year-month-day
4 digit year-month
4 digit year
month-day
4 digit year/month/day
4 digit year/month
4 digit year
month/day

Your 1-1-2019 is likely being interpreted as 1-1 and the -2019 interpreted as a keyword.

Try altering your date format to one of the above and see if that improves things.

-Kirk

[carlseibert]

Yup! When I do it right it works.

And I rechecked. It IS correct in the example pane. I had looked right at it and still typed it backwards. Repeatedly.

Thanks and sorry for my nincompoopery!