Based on the info from Robert that docs have been sealed, I wouldn't do it this way ever in a view.
-zh On Tue, Jun 12, 2012 at 3:52 AM, bryan rasmussen <[email protected]> wrote: > So deployment should take into account spidermonkey differences if I > do it this way? > > Thanks, > Bryan Rasmussen > > On Tue, Jun 12, 2012 at 9:08 AM, Robert Newson <[email protected]> wrote: >> Hm, the doc object should be sealed, though. You won't be able to >> modify it reliably (it'll depend on whether you link against a >> spidermonkey that supports object sealing, which is most, but not all, >> of them). >> >> B. >> >> On 12 June 2012 07:44, bryan rasmussen <[email protected]> wrote: >>> hey yeah, that should work fine, I just set it to 'private' when I >>> emit. Damn, I should have thought of that, down in the code too long >>> is making me tunnel visioned :) >>> >>> >>> thanks, >>> Bryan Rasmussen >>> >>> On Tue, Jun 12, 2012 at 4:03 AM, Zera Holladay <[email protected]> >>> wrote: >>>> Try deleting the username field in the view and then emitting the doc? >>>> I don't know why it would work, but I don't know why it wouldn't >>>> either. Just an idea. >>>> >>>> -zh >>>> >>>> On Mon, Jun 11, 2012 at 8:45 PM, Robert Newson <[email protected]> wrote: >>>>> why not use a show or list function that removes that field? >>>>> >>>>> B. >>>>> >>>>> On 12 June 2012 01:37, Jens Alfke <[email protected]> wrote: >>>>>> >>>>>> On Jun 11, 2012, at 4:29 PM, bryan rasmussen wrote: >>>>>> >>>>>>> Does couchdb have some sort of higher level way of doing this that >>>>>>> will have better performance than just looping through the object and >>>>>>> copying over every property unless it is the username one? >>>>>> >>>>>> Is the performance of that a problem? Remember, the map function is only >>>>>> run when a document is updated. It's generating an index, not performing >>>>>> the query. >>>>>> >>>>>> —Jens
