Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 29179 invoked from network); 8 Jan 2009 16:00:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jan 2009 16:00:02 -0000 Received: (qmail 15641 invoked by uid 500); 8 Jan 2009 15:59:59 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 15612 invoked by uid 500); 8 Jan 2009 15:59:59 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 15601 invoked by uid 99); 8 Jan 2009 15:59:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2009 07:59:59 -0800 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.200.175] (HELO wf-out-1314.google.com) (209.85.200.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jan 2009 15:59:51 +0000 Received: by wf-out-1314.google.com with SMTP id 28so10346142wfc.29 for ; Thu, 08 Jan 2009 07:59:29 -0800 (PST) Received: by 10.114.137.16 with SMTP id k16mr16134497wad.189.1231430369594; Thu, 08 Jan 2009 07:59:29 -0800 (PST) Received: by 10.114.254.6 with HTTP; Thu, 8 Jan 2009 07:59:29 -0800 (PST) Message-ID: <64a10fff0901080759k4e36bc4bx96b5d5465f54997f@mail.gmail.com> Date: Thu, 8 Jan 2009 10:59:29 -0500 From: "Dean Landolt" To: user@couchdb.apache.org Subject: Re: drill into a doc with a GET? In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_161020_22546457.1231430369582" References: <013C8232-C1A7-4C69-8996-21C86B41B340@koberg.com> <5F4CD013-AB8B-4570-8106-6DCE08FBA550@koberg.com> <60226249-2781-43AF-86B8-17940B3B9251@koberg.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_161020_22546457.1231430369582 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > Here you go :) > > http://www.w3.org/TR/xquery-update-10/ I was going to pass that in the first time the debate raged but decided it was best for me to stay the hell out (I have no need for JSON-update). But as far as guidance for an RFC goes, it could be a great start. While xquery is a ugly beast, the xquery-update facility is fairly elegant. The problem is it requires something like xpath to work, and while json-path exists, evaluation is not pure json and requires a javascript interpreter, which breaks with couch's design philosophy. > Seriously though, I am thinking I need at least one more layer of > discrimination - a collection (similar to XPath & XML DBs). I think CouchDB > is really nice, but not for my current wants/needs. > > best, > -Rob > A collection in xquery terms is really nothing more than a tag with a few supporting APIs. What does it gives you that you can't get right out of the box with couch? ------=_Part_161020_22546457.1231430369582--