n the documents ?
2010/11/4 Siegmund Führinger
> hi!
>
> On Wed, Nov 3, 2010 at 5:32 PM, sgoto wrote:
>
> > hi couchdb,
> >
> >are there any plans for supporting multi columns in couchdb (eg
> update
> > one column for a key without re writing the entire
hi!
On Wed, Nov 3, 2010 at 5:32 PM, sgoto wrote:
> hi couchdb,
>
>are there any plans for supporting multi columns in couchdb (eg update
> one column for a key without re writing the entire row) ?
>
there is no way to prevent a re-writing of a complete document, but with a
Nice discussion here!
I have thought about this kind of design, but thus I need to get a
searchable indexed View from that View which is not possible in
current CouchDB design.
However, I still think to manage data as small change sets like Git
is the way to go. It fits the immutable structure of
On Wed, Nov 3, 2010 at 11:54, Mark J. Reed wrote:
>
> Anyway, CouchDB doesn't have this feature. I disagree with sgoto that
> the crash-only design prohibits it, however. Certainly the server
> would have to append the entire modified record to the data store, but
> that doesn't mean the entire d
On Wed, Nov 3, 2010 at 12:32 PM, sgoto wrote:
> are there any plans for supporting multi columns in couchdb (eg update
> one column for a key without re writing the entire row) ?
I think it's misleading to refer to CouchDB documents as "rows", since
each of them can hav
On Wed, Nov 3, 2010 at 1:32 PM, sgoto wrote:
> hi couchdb,
>
> are there any plans for supporting multi columns in couchdb (eg update
> one column for a key without re writing the entire row) ?
I am not a CouchDB guru, but from reading the docs it is clear to me
the answer is
hi couchdb,
are there any plans for supporting multi columns in couchdb (eg update
one column for a key without re writing the entire row) ?
sam
--
f u cn rd ths u cn b a gd prgmr !
