Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of randall.leeds@gmail.com
 designates 209.85.200.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=NQCER+f/PfcaXFqEC5VpWrvzHBgJQ2s0XTKbbRbcalUTcKyX4X7Cn7+QE5iqEb9T5B
         KZ28jqsqpIBxDz8sajwpsdee53V5iKqDbKl1/l2GXOmCfaeIvhTeCqzyQtfNxDGpD7cl
         Qv/qpkxPfTRSDYc6+htwn5JAo2pWRa8Pch+qQ=
Message-ID: <ec7a93a0807282225n782aee97wd5b65a46444cf2c4@mail.gmail.com>
Date: Tue, 29 Jul 2008 01:25:28 -0400
From: "Randall Leeds" <randall.leeds@gmail.com>
To: couchdb-dev@incubator.apache.org
Subject: Re: CouchDB Success Stories
In-Reply-To: <e282921e0807281944u73fd11f1ga9e418d791cc0ae1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_23384_6909428.1217309128454"
References: <5879e51d0807281729h490b946wc331b279403e8e8e@mail.gmail.com>
	 <ad0d04230807281755g22778367qadca56d473804f99@mail.gmail.com>
	 <e2111bbb0807281803g3851308bj5c6ad94b3663955a@mail.gmail.com>
	 <e282921e0807281944u73fd11f1ga9e418d791cc0ae1@mail.gmail.com>

------=_Part_23384_6909428.1217309128454
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Mon, Jul 28, 2008 at 10:44 PM, Chris Anderson <jchris@grabb.it> wrote:

> On Mon, Jul 28, 2008 at 6:03 PM, Paul Davis <paul.joseph.davis@gmail.com>
> wrote:
> > Just had a thought, with 20 views, how do you (and anyone else) manage
> > to keep that straight?
>
> I have a script that keeps them on the filesystem as .js files (for
> syntax highlighting and version control).
>

I've been using couchdb-python and storing my views in .py files as follows:
The design doc stores functions whose map code reads "from my_views_module
import my_map_function"
I find this to be an elegant answer to the problem you're bringing up, if
you're willing to write views in python.

I've been thinking about writing a TextMate bundle to handle embedded
> JS in Ruby (because I think it might be clearer to keep the views near
> the functions that utilize them).


The application using the database is also written in python, so my views
are kept alongside the rest of the project's modules.
It is also possible to unit test your view functions this way, as part of
the test suite for your whole application. Very clean.

I don't mean this to be a shameless python plug, but I do really like the
way this works out!

Randall Leeds

------=_Part_23384_6909428.1217309128454--