Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 clement@challet.eu does not designate 88.191.97.33 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: rewrite rules for alphabetic browse
From: Clement Hallet <clement@challet.eu>
In-Reply-To: <BANLkTinHWDK02nVCQQN4L1VcJa3+9BH77w@mail.gmail.com>
Date: Tue, 21 Jun 2011 16:29:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9437EA4B-96D6-499E-81F5-C5A422D54066@challet.eu>
References: <BANLkTinHWDK02nVCQQN4L1VcJa3+9BH77w@mail.gmail.com>
To: user@couchdb.apache.org

Hello Gabriel,

Why not making a key using only the first letter ?=20

 function(doc) {
   if (doc.type && doc.name) {
     emit([doc.type, doc.name[0]);
   }
 }


and querying it with that key =3D ["artist","a"]


--=20
Cl=E9ment

Le 21 juin 2011 =E0 16:18, Gabriel Farrell a =E9crit :

> I'm putting together a site where I have artists and works of art. I
> would like to browse those artists and works alphabetically, with URLs
> like http://example.com/artists/a and http://example.com/works/b. I
> have a view called type_name:
>=20
>  function(doc) {
>    if (doc.type && doc.name) {
>      emit([doc.type, doc.name]);
>    }
>  }
>=20
> My "artists" list renders the results from that view in a template. I
> can get the first page of artists with a rewrite like this:
>=20
>  {
>    "from": "artists/a",
>    "to": "_list/artists/type_name",
>    "query": {
>      "startkey": ["artist", "a"],
>      "endkey": ["artist", "aZZZZZ"]
>    }
>  },
>=20
> How would I generalize this for all letters of the alphabet? I want to
> do something like the following, but the last ":startkey" isn't
> substituted:
>=20
>  {
>    "from": "artists/:startkey",
>    "to": "_list/artists/type_name",
>    "query": {
>      "startkey": ["artist", ":startkey"],
>      "endkey": ["artist", ":startkeyZZZZZ"]
>    }
>  },
>=20
> I can achieve something close by extending the URL to
> http://example.com/artists/a/aZZZZZ and using the following rewrite:
>=20
>  {
>    "from": "artists/:startkey/:endkey",
>    "to": "_list/artists/type_name",
>    "query": {
>      "startkey": ["artist", ":startkey"],
>      "endkey": ["artist", ":endkey"]
>    }
>  },
>=20
> The URL is uglier but it works. Is there any way to make the shorter
> URL work? Frankly, I think some of my trouble is that, coming from
> other web frameworks, I'm not used to my URLs being constrained in
> this way. I want to be able to grab the request path, munge it all
> over with JavaScript, then send it on to my lists, shows, views, etc.