Looking at Show documentation and running a quick test I don't think this helps as Show has to be referenced by a doc._id or view key. If these aren't provided it returns null. This makes sense as its for generation of a html, XML page/doc etc.
So I'd have to get a list of all doc ID's I want and then call the show function for each and to get a filtered list I need a view. Mike -----Original Message----- From: Mike Kimber [mailto:[email protected]] Sent: 24 May 2012 10:47 To: [email protected] Subject: RE: Am I doing something fundamentally wrong? Aurélien, Thanks for the response and apologies I didn't get a notification (e-mail) of my original post (or the 2nd one) or your response. When I look at my original post in Google Reader is has "An error occurred while fetching this message, sorry !", so there must be something in the e-mail that the mailing list system does not like. In response to your original response " I'm a bit puzzled by the fact that your map functions use the document ID". I do this because I load the data into Luciddb and this allows me to join between tables. This is not my end game this is just a compromise due to the time it takes to generate a view and my need to play/discover with the data. I will look at show to see if It helps, however it does not really answer my original questions and it does not remove the more general issue that view build takes a very long time, it only uses a single CPU and uses a bucket load of space even with compression on (no idea why when it has a lot less data than the original) Thanks Mike -----Original Message----- From: Aurélien Bénel [mailto:[email protected]] Sent: 24 May 2012 07:40 To: [email protected] Subject: Re: Am I doing something fundamentally wrong? Hi Mike, > Didn't seem to get there first time so having another go As I wrote in my earlier post, the use of 'map' functions in both of your examples is overkill. Use 'show' functions instead.They won't require an index to be built. Regards, Aurélien
