Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jrhuggins@gmail.com
 designates 209.85.221.10 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:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=Uat4nfIQshouk6TYozNjRhde9v7/uJfnLBO1Go8DFMM9lP3NaX/Bprp6oUbeGlfLM1
         mL6Gx3lJb3EdkmXqN4kUt3UqMOzv2z3ghLNMogZjht1yeO73KuamIzVizyzWlvb866zX
         tYkUYQ2foI+kr+k+HSQyPLnMIs+j1TCNXuP/w=
Message-ID: <53b9568a0812011907u25e99f06s7ee1c036356942df@mail.gmail.com>
Date: Mon, 1 Dec 2008 21:07:06 -0600
From: "Jason Huggins" <jason@jrandolph.com>
Sender: jrhuggins@gmail.com
To: couchdb-user@incubator.apache.org
Subject: Re: Auto-adding additional fields on PUT/POST? (datetime stamps)
In-Reply-To: <493487C8.5060206@silencegreys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <53b9568a0812010829n49ce2eebl89419e5db0b536a4@mail.gmail.com>
	 <493487C8.5060206@silencegreys.com>

On Mon, Dec 1, 2008 at 6:56 PM, Jedediah Smith
<jedediah@silencegreys.com> wrote:
> The new validation functions might be able to do this for you if they are
> allowed to modify the document. Whether or not they are was asked on the dev
> list but not answered. I hope they are as that would be endlessly useful. It
> would be *really* neat if a function could also handle merging for revision
> conflicts.

Are validation functions in trunk or a released version?... or still
on the drawing board? (I suppose I should switch to the dev list to
ask that question to a more targeted audience.) :-)

I have another idea for tracking timestamps and other meta-data.  I
think I'll create a meta-data database for each "real" database.
Since I'd like to give my users free reign to edit their own documents
in the real database, but *not* be able to edit createdAt and
lastModified timestamps. So, with a meta-data db, I can set it up so
only my server has write permission to that meta-db, but the user can
read from it.

The downside is that combining the data and meta-data into a unified
view of the document would have to happen on the client side, not on
the couchdb side, since (as I understand it), couchdb can't do
cross-database map/reducing views.

- jason huggins
  http://saucelabs.com