Hi, On Fri, Aug 8, 2014 at 2:57 AM, Davide Giannella <[email protected]> wrote: > Hello Justin, > > On 07/08/2014 15:12, Justin Edelson wrote: >> Hi Davide, >> Could this be configurable on the QID? > I was thinking on the same line. We create the code so almost everything > is possible. :) > > What would it be a good default? Definitely when sorting I don't care of > the millisecond precision. In my experience when retrieving content > ordered by dates > > select * from [nt:unstructured] order by jcr:lastModified desc
In my experience, you would use minute precision for range queries and second precision for ordering. So I guess this means that second precision would be the best default and then allowing minute precision to be used as an optimization for an index which you knew was only going to be used for selection purposes (or ms for other cases where you needed more precise ordering / data selection). Justin > > when presented to the end user a precision of a minute would suffice. > This means that if you truncate it to the minute you'll have correct > sorting up to the minute but if you had 1k nodes added within that > minute you won't be able to predict the order of that bucket. > > Thoughts? > > D. > >
