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 kxepal@gmail.com designates
 209.85.210.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABBNpWsxpOvEehY7qx+iqXSUmiQ=PmW_j4ysrypkLXuWHWT9qQ@mail.gmail.com>
References: 
 <CABBNpWsxpOvEehY7qx+iqXSUmiQ=PmW_j4ysrypkLXuWHWT9qQ@mail.gmail.com>
Date: Wed, 2 Nov 2011 15:57:51 +0400
Message-ID: 
 <CAHdjipLMO+aENY=eBoMeNrgT6uo3Yu5MaLJTzq03_Lz3ScMM0A@mail.gmail.com>
Subject: Re: Best way to model historical data
From: Alexander Shorin <kxepal@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

"Each document represents some completed state(event - it just was as
it is and history couldn't be changes) and doesn't affected from
external data" - start from this point(; To reduce document size you
may include related document _id and all vital fields that shouldn't
be changed in time for it.

Another approach is keeping references both to _id and _rev of related
document, but all would be broken if someone runs database compaction
(also this method doesn't works for views).

--
,,,^..^,,,


On Wed, Nov 2, 2011 at 2:20 PM, couchdb - Andr=C3=A9s Orencio - lodopidolo
<dir.couchdb@orencio.org> wrote:
> Hello. I'm new in couchdb.
>
> I have some questions but I'm going to put them in separate threads.
>
> For this, I want ask you which is the better way to store documents and i=
ts
> historical states.
>
> For example, I have products documents and categories documents. Products
> has one or more categories. This "relation" may change in the time, and
> product characteristics can change to.
>
> I want to store all document changes (categories too).
>
> Which is the better way to do this?
>
> Thanks you.
>