tag:blogger.com,1999:blog-1811678269659949780.post142910188785103169..comments2009-05-03T00:25:20.221-05:00Comments on This Blog is for Closers Only: It's all about document design with CouchDBBradfordWhttp://www.blogger.com/profile/15452198763280555810noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1811678269659949780.post-89971850872763438002008-07-06T21:14:00.000-05:002008-07-06T21:14:00.000-05:00Thanks for the comments guys. I decided to bite o...Thanks for the comments guys. I decided to bite off far more than I can chew and attempt to implement the multiple key query we spoke of on the mailing list. I've just returned from a weekend away so I'll follow up with the proposed fix.BradfordWhttps://www.blogger.com/profile/15452198763280555810noreply@blogger.comtag:blogger.com,1999:blog-1811678269659949780.post-86081310003417916952008-07-03T12:45:00.000-05:002008-07-03T12:45:00.000-05:00Adam, dynamic views are never a good idea except f...Adam, dynamic views are never a good idea except for development. The solution is either to use multiple queries to that view or use a fulltext search.JanLhttps://www.blogger.com/profile/04778932038681738668noreply@blogger.comtag:blogger.com,1999:blog-1811678269659949780.post-69082691070321406052008-07-03T11:53:00.000-05:002008-07-03T11:53:00.000-05:00I'm pretty certain the answer here is a dynamic vi...I'm pretty certain the answer here is a dynamic view. Since you can't pre-compute the result set (since the tag list is variable) you won't be taking any kind of performance hit.<BR/><BR/>Essentially, abstract that view snippet into a method, and then just call it with the right arguments, compose the view, and submit it to couchdb for immediate processing.<BR/><BR/>I think. :)Anonymousnoreply@blogger.com