I know this is cheating, but have you considered simply using the NoteID instead of the UNID? The NoteID is only 8 chars instead of 32, this giving you four times as many docs that can be processed from a view via standard URL parameters before you hit the 1024 limit (I can get up to 50 docs this way, and I don't allow views longer than that).
That method doesn't have the other advantages of Jake's solution, but it might be easier for some people.
FYI: NoteID isn't unique across replica db's, but it's unique within an individual db. So unless you've got a load-balanced cluster running, it's just as valid as a UNID. If you DO have a load-balanced cluster running, you can afford to hire Jake to write something much cooler!
I know this is cheating, but have you considered simply using the NoteID instead of the UNID? The NoteID is only 8 chars instead of 32, this giving you four times as many docs that can be processed from a view via standard URL parameters before you hit the 1024 limit (I can get up to 50 docs this way, and I don't allow views longer than that).
That method doesn't have the other advantages of Jake's solution, but it might be easier for some people.
FYI: NoteID isn't unique across replica db's, but it's unique within an individual db. So unless you've got a load-balanced cluster running, it's just as valid as a UNID. If you DO have a load-balanced cluster running, you can afford to hire Jake to write something much cooler!
Looking forward to the article, Jake!