Date Search - Include Today

[lazorbeam]

Hey everyone. I'm running into a problem getting my date search in Calibre right and am hoping someone wiser than I has the fix.

I would like to set a date search for all books that have been added within the last two days including books added today. Using date:<2daysago I get books added from the last two days except for any that were added today. Using date:today I do get those books added today (but only those of course). Closing the current session and restarting Calibre does not change whether the books show up in the 2daysago search.

What I'd like is for all books within the last two days (or whatever timeline) to show up. I tried date:<=2daysago would do this (thought logically that doesn't fix it), but the search results were identical to date:2<daysago. Long shot but date:today and date<2daysago results in a green search bar (valid) but no books found.

I'm sure I'm just missing something little but any help is appreciated! It throws me off a bit because less than/before a certain amount should naturally include EVERYTHING before that (which includes today books).

If it matters, I use as a Virtual Library search. This is working fine, it's just not inclusive. THANKS.

[PeterT]

Are you sure you don't mean date:>2daysago

With me I do see books added today as well as in the last few days.

[lazorbeam]

HEY. I think that works. I was regarding this as < equals less than which, here, equals more recent, but maybe it's more of a linear time scale?

This seems good though. When I put in date:>10days, I found only a few books in the results all of which were recently added.

What a simple fix. It confuses me because I was sometimes getting weird search results before when I was fiddling with >,<,=,etc before but I think's related to something else. (I also made a new column a few days ago and it sort of refreshed my whole library which may be affecting things and relative dates).

Thanks for the quick and embarrassingly easy solve! I appreciate your help!

[Sabardeyn]

Originally Posted by lazorbeam

(I also made a new column a few days ago and it sort of refreshed my whole library which may be affecting things and relative dates).

Yes, this is a known issue. Calibre is working exactly as intended and this change to the date is needed in order to make sure that other functions operate correctly. However, as you've found, it does confuse matters because while you don't think you've changed anything, calibre believes you have, and will/won't find books accordingly.

The only real way around this is to create a custom column for a date and to manually change that date. Which is highly unlikely to be implemented because of the extra work.

[lazorbeam]

Yes, definitely unlikely to be implemented. That's okay though. It surprised me but no big deal. Now that I have the date sort figured out, I don't think it matters much.

Thanks again!