Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of simon@cloudant.com designates
 74.125.83.52 as permitted sender)
Date: Fri, 8 Jun 2012 03:35:13 +0100
From: Simon Metson <simon@cloudant.com>
To: user@couchdb.apache.org
Message-ID: <C379B68DAE7840A494E7D59EEE3F6CBD@cloudant.com>
In-Reply-To: 
 <CALp38EP8roLd8f=HzhcWD5Zpw5Emb95s4SOeNCJLnfasFr0xtA@mail.gmail.com>
References: 
 <CALp38ENfFkmUgRB7cTTGEeX6oukV=7+YuYhM3uHeZfHga4h_jQ@mail.gmail.com>
 <CACrj35FNrx5xgkD73GgYWBgrDozeXVO4yJkQgfM5ECa3xV1Btw@mail.gmail.com>
 <CALp38EP8roLd8f=HzhcWD5Zpw5Emb95s4SOeNCJLnfasFr0xtA@mail.gmail.com>
Subject: Re: Adding vs replicating documents
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4fd164e1_77263b8a_11e68"

--4fd164e1_77263b8a_11e68
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi, 
Can't your program write to a local CouchDB instance instead of a file?
Cheers
Simon 


On Friday, 8 June 2012 at 03:31, Luca Matteis wrote:

> I use my own IDs which are stored in the JSON file. I can't use futon.
> I'm stuck with this JSON file (which is generated programmatically
> btw). I was just wondering if there was an easy way to use the
> replication API and check if this JSON file has changes, and upload
> only those, instead of re-uploading everything.
> 
> On Fri, Jun 8, 2012 at 4:14 AM, Mark Hahn <mark@hahnca.com (mailto:mark@hahnca.com)> wrote:
> > You can't update a document unless you have the id.  Do you have a view set
> > up to find what you want?  If so pull them up and edit them in futon.
> > 
> > Usually one would edit the docs in the db directly using futon, not change
> > the original data.
> > 
> > On Thu, Jun 7, 2012 at 6:35 PM, Luca Matteis <lmatteis@gmail.com (mailto:lmatteis@gmail.com)> wrote:
> > 
> > > I have a file that contains lots of JSON documents - probably around
> > > 1gb of data.
> > > I uploaded this file to my server's Couch instance (on the cloud)
> > > using the Bulk API.
> > > Now I need to re-upload it because I've made some changes to the file
> > > - I've added some documents, deleted some, and edited a few.
> > > 
> > > My question is, can I avoid sending over the wire the 1gb of data
> > > every time I make modifications to it?
> > > 
> > > I've thought about setting up a local Couch instance on my computer,
> > > upload data there, and then replicate it to my Couch instance, so that
> > > only changes get sent over the wire... but was wondering if there was
> > > an easier way instead of having to install CouchDB on my computer.
> > > 
> > 
> > 
> 
> 
> 


--4fd164e1_77263b8a_11e68--