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 metalelf0@gmail.com designates
 74.125.46.30 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version
         :content-type:references:x-google-sender-auth;
        b=jVYpVILt011bKu0JtIpv4sj0WyZlKt8wNA2MO2AGZKQtqtD/Y5QrazXNSSwOxO90XK
         lBQ7id80pJiC8ilJwcx1cAVt2C0TJsPI4072xixQST5dYpOi1cye+aEBMCMW3FY+DABN
         BjEM957OU8TxWbTAkrIOeIWHKmyzL8kXPuZkE=
Message-ID: <7d8fb2e90812162337o3d08430dwc09af6d73e662d95@mail.gmail.com>
Date: Wed, 17 Dec 2008 08:37:17 +0100
From: "Andrea Schiavini" <a.schiavini@sourcesense.com>
Sender: metalelf0@gmail.com
To: user@couchdb.apache.org
Subject: Re: General Q about CouchDB
In-Reply-To: <F966D10F-78E0-43BB-BE02-BCEF6A2367B9@prima.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2452_19096077.1229499437977"
References: <389be9770812161146ldcbd435l32300db81573ebd0@mail.gmail.com>
	 <e282921e0812161151y40751b9fi2acf02374a202a24@mail.gmail.com>
	 <389be9770812161154r507c57b5ja6bfe298071d9731@mail.gmail.com>
	 <F966D10F-78E0-43BB-BE02-BCEF6A2367B9@prima.de>

------=_Part_2452_19096077.1229499437977
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

In the second approach described in this article, posts are separated from
comments. But isn't this in contrast with the impossibility of CouchDB to
update atomically several documents? It could lead to a loss of database
integrity, if in example an user deletes an article while another one
updates a related comment. Shouldn't it be encouraged to keep related
informations in the same document?

Andrea Schiavini

2008/12/17 Jan Lehnardt <jan@prima.de>

>
> On 16 Dec 2008, at 20:54, Christopher McComas wrote:
>
>  Chris,
>> Thanks. One question, concern I might have with that would be just
>> spelling
>> something differently, but that shouldn't be too big of an issue.
>>
>> To my next question, what would be the best way to structure comments for
>> a
>> blog post, where they have their own author, timestamp, and entry? Again,
>> this is fairly straight-forward with a relational db using a foreign key.
>>
>
> Same concept ;)
>
> See http://www.cmlenz.net/archives/2007/10/couchdb-joins for details.
>
> Cheers
> Jan
> --
>
>
>
>
>>
>> Thanks,
>>
>> On Tue, Dec 16, 2008 at 2:51 PM, Chris Anderson <jchris@gmail.com> wrote:
>>
>>  On Tue, Dec 16, 2008 at 11:46 AM, Christopher McComas
>>> <mccomas.chris@gmail.com> wrote:
>>>
>>>> Would it be wrong to try to do the category piece as related in CouchDB?
>>>> What would be the best way to do it, so that you can have a page,
>>>> myblog.com/categories/this-category/ that'd then display all the
>>>> entries
>>>>
>>> for
>>>
>>>> that category? What would be proper?
>>>>
>>>
>>> Having a category field on the blog post itself is a fine way to do this.
>>>
>>> Eg:
>>>
>>> {
>>> "title":"Blah",
>>> "author":"Chris",
>>> "category":"music",
>>> "date": ...
>>> }
>>>
>>> Writing a view that sorts posts by category and date would be simple
>>> with this sort of data structure. Of course if you wanted to rename a
>>> category later you'd need to touch all the documents that listed it,
>>> so this solution is more like tagging than categories, but should
>>> fulfill the need.
>>>
>>>
>>> --
>>> Chris Anderson
>>> http://jchris.mfdz.com
>>>
>>>
>

------=_Part_2452_19096077.1229499437977--