Hi. I am equally concerned about the issue Tim has raised. I am
disappointed because I was also counting on the functionality that
couch possessed going forward. We are loosing something here, though
it may not appear on the surface as being that important (possibly
because the apps with this use case in mind might be in the
minority). Despite this, it is difficult to accept the recent change
as a new limitation on current and future couch app development. I am
really hoping that this can be resolved in some way to accommodate
such scenarios as Tim has spent his effort describing. Forking couch
makes no sense to me at all. Many thanks.
Regards,
David
On 25-Mar-09, at 9:50 AM, Tim Parkin wrote:
The upshot appears to be that CouchDB is limited to only changing a
single document at a time through a user interface (unless you want to
add lots of work to handle conflicts).. Could I have a confirmation of
this so I can blog about it. It's a pretty fundamental restriction and
one I'm sure people who want to use CouchDB would want to know about.
Tim
