Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Updating an embedded document (MongoJsonObjectField)

Received: by 10.42.69.73 with SMTP id a9mr5619752icj.30.1350294363072;
        Mon, 15 Oct 2012 02:46:03 -0700 (PDT)
X-BeenThere: liftweb@googlegroups.com
Received: by 10.50.190.136 with SMTP id gq8ls2853225igc.4.canary; Mon, 15 Oct
 2012 02:45:59 -0700 (PDT)
Received: by 10.43.71.18 with SMTP id yi18mr112592icb.21.1350294359664;
        Mon, 15 Oct 2012 02:45:59 -0700 (PDT)
Received: by 10.43.71.18 with SMTP id yi18mr112590icb.21.1350294359654;
        Mon, 15 Oct 2012 02:45:59 -0700 (PDT)
Return-Path: <maarten.koopm...@gmail.com>
Received: from mail-ia0-f175.google.com (mail-ia0-f175.google.com [209.85.210.175])
        by gmr-mx.google.com with ESMTPS id ge7si779594igb.0.2012.10.15.02.45.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 15 Oct 2012 02:45:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of maarten.koopm...@gmail.com designates 209.85.210.175 as permitted sender) client-ip=209.85.210.175;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of maarten.koopm...@gmail.com designates 209.85.210.175 as permitted sender) smtp.mail=maarten.koopm...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ia0-f175.google.com with SMTP id b35so4155148iac.20
        for <Liftweb@googlegroups.com>; Mon, 15 Oct 2012 02:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=fGv1SOr4Jk0V6D8srWgVxWavyCteA8+nP99bFfQNZ9w=;
        b=FEDFCuQCxk5f7m60Uv1/NxpXSRYsW+qYy7Vvks9p+Ed84eXdZkEZfX85A73uruJzUU
         PcApxSUt3hvxwmzx4kVBWsFQaFo06nEg1jJm860YeYRn+kphwnAhEYpOBRg2ffBU+nsD
         JuUiwcRVr8kyz6uVDinDl1qjrrwzEpOjTEXGBlgPzQwETw3HgYyCl5+eRkDTc5o6vLNz
         C5vKrios57R7Ry/OCNLQDz62shQth0Wx6zvqNWM7zEk0Cj55z25Dy80FT1A+3SJUs4D8
         im9klE2lJ/pvsgHrVNC5DDFnL5D6UFuJ1THXQqKwXzFNWKDelaR9llzIlex3uHrDUaEe
         bJfA==
MIME-Version: 1.0
Received: by 10.43.98.196 with SMTP id cp4mr2087245icc.25.1350294359496; Mon,
 15 Oct 2012 02:45:59 -0700 (PDT)
Received: by 10.50.183.131 with HTTP; Mon, 15 Oct 2012 02:45:59 -0700 (PDT)
Date: Mon, 15 Oct 2012 11:45:59 +0200
Message-ID: <CAJ9WAGdajGNEE2CRe+2x23x8HuVyb27m70ZjVMH2T2Vgo+S...@mail.gmail.com>
Subject: Updating an embedded document (MongoJsonObjectField)
From: Maarten Koopmans <maarten.koopm...@gmail.com>
To: Liftweb@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Subjects says it hopefully all: what is the most elegant way to update
(i.e. add/remove items to/from) a MongoJsonObjectField?

I only found solutions that force you to build new lists on the client
side - which I hoped to avoid. Because that would be quite dangerous
wrt locking etc (concurrent updates).

Any feedback appreciated - and I'll add it to the Wiki as soon as I
figure it out.

Thanks!

--Maarten