Strange date query behavior

[Mauro Servienti]

Hi,

 

Running 701, cannot update to a newer build at the moment.

 

I have an index that produces a projection that has a lot of properties among which there are some date/time properties:

 

"LastMessageDeliveredAt": "2012-04-10T08:42:27.8296290+00:00"

(in json seen from the studio)

 

Now, issuing this query (from the studio):

LastMessageDeliveredAt: [20100201 TO 20120201]

 

Does _not_ filter out the document that has the above value, if I issue this query

LastMessageDeliveredAt: [20100201 TO 20110201]

 

Changing the year from 2012 to 2011 documents are correctly filtered.

 

Any idea?

.m

 

 

[Mauro Servienti]

If I change the Lucene query to this:

LastMessageDeliveredAt: [2010-02-01 TO 2012-02-01]

 

It works as expected, now running the same using Linq:

 

var limit = DateTimeOffset.Now.AddMonths( -2 ).Date;

mailboxSession.Query<BlaBla, BlaBla>().Where( c => c.LastMessageDeliveredAt <= limit )

 

does not work, how can I see which Lucene query gets produced?

 

.m

[Matt Warren]

To see the Lucene query you can do this:

var queryText = mailboxSession.Query<BlaBla, BlaBla>()

                                          .Where(c => c.LastMessageDeliveredAt <= limit)

                                          .ToString();

[Matt Warren]

Also you might want to use the Raven.Abstractions DateTools class to do the conversion for you, see https://github.com/ayende/ravendb/blob/master/Raven.Abstractions/Linq/DateTools.cs. That way you'll know the dates are converted properly.

[Oren Eini (Ayende Rahien)]

What index is this using? The only time the index would retain dates in this format:  : [2010-02-01 TO 2012-02-01] 

is when you are saving the dates using not analyzed.

[Mauro Servienti]

Amazing, that did the trick, I did not know.

What should be the value? Analyzed or Default?

[Oren Eini (Ayende Rahien)]

For dates, probably default.