Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of siriele2x3@gmail.com
 designates 209.85.216.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <683C33A5-8891-47CF-806F-D0A5623AB845@openssl.it>
References: 
 <CAPNuaChd8NnZwCLOMm=GVLSUWQ38=hxp8JWtRErofqOdsgH_EA@mail.gmail.com>
	<683C33A5-8891-47CF-806F-D0A5623AB845@openssl.it>
Date: Wed, 5 Mar 2014 09:54:36 -0800
Message-ID: 
 <CAPNuaCg7yqhLS74U1LzLG1YSBPZksyiWH49zHa73Rcm9Cq2rXg@mail.gmail.com>
Subject: Re: Storing a doc I'd as json array string
From: Stanley Iriele <siriele2x3@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001a1133bce2c6ec0804f3dfb669

--001a1133bce2c6ec0804f3dfb669
Content-Type: text/plain; charset=ISO-8859-1

Thanks... I know doc ids have to be strings so when I "array string" I
meant json encoded string... It seems to work just fine so far but it
doesnt look too pleasant but I can't risk the idea of delimiter
collision...at all... I guess I could store the hash of those values or
something
On Mar 5, 2014 7:53 AM, "Marcello Barnaba" <vjt@openssl.it> wrote:

>
> On Mar 05, 2014, at 07:27, Stanley Iriele <siriele2x3@gmail.com> wrote:
>
> > I want to store a document for a particular game... Version...and
> > key...where key could be any string. I want there to be a key collision
> on
> > insert
> >
> > I don't want to make up some delimeter because that wouldn't go so well....
>
> If only the "key" field is out of your control and you can't assure the
> delimiter will not appear in it, you can put this field last. Then, when
> parsing the id, you split it up to the second delimiter.
>
> --
> ~ vjt@openssl.it
> ~ http://sindro.me
>
>

--001a1133bce2c6ec0804f3dfb669--