These second level caches could be query-able just like views are,
but one
level removed. We could even specify them with permanent javascript
methods
so you could query on them instead of the underlying views. What do
you
guys think?
This is exactly the kind of thing I'd like to use in
I ended up just doing all the queries every time, sorting the results, and
clipping them. That means I fetched all the pages on each page. It was
fast enough.
An easy improvement would be to do the multiple queries, sort them, and then
cache that somewhere similar to a view in case the user asks
On Sun, Nov 16, 2008 at 7:54 PM, Nicholas Retallack
<[EMAIL PROTECTED]> wrote:
> We could do 3 queries anyway, each with the maximum number of documents on
> the page, then sort them ourselves and throw away the extras. This gets
> messy fast though, when you try to keep track of where to start th
Hi Nicholas,
I just ran into the sort by date thing last night. My solution was:
function(doc) {
time = doc.created_at.replace(/\D/g, "");
emit([doc.document_id, time], doc)
}
to convert my time stamp (also in the form of a string like yours)
into a number which could be sorted.
Regarding p
