View Single Post
Old 06-04-2010, 04:10 PM   #11
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,453
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by theducks View Post
Does the Query interface have "Today" (date) concept, where our query could be timestamp:>=(today-90) so we could have a saved definition of "Recent" without having to worry about the date (Sort of what happens in the "Catalog")
Date queries support all relational operators (< <= = != > >=). Search syntax is date:RELOPdate_term. A date_term specifies the date being compared against, and can be one of:
  • today
  • yesterday
  • thismonth
  • Ndaysago. N is a number. Your example would use 90daysago
  • a year (4 digits)
  • month/year (and year/month) where month is 1 or 2 digits
  • day/month/year (order is locale dependent), where day and month are 1 or 2 digits.
Your query would be expressed as date:>=90daysago
chaley is offline   Reply With Quote