Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F4E49201 for ; Tue, 21 Feb 2012 22:23:14 +0000 (UTC) Received: (qmail 17946 invoked by uid 500); 21 Feb 2012 22:23:14 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 17905 invoked by uid 500); 21 Feb 2012 22:23:14 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 17897 invoked by uid 99); 21 Feb 2012 22:23:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 22:23:14 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryan.ramage@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vx0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Feb 2012 22:23:09 +0000 Received: by vcbfo1 with SMTP id fo1so6414056vcb.11 for ; Tue, 21 Feb 2012 14:22:49 -0800 (PST) Received-SPF: pass (google.com: domain of ryan.ramage@gmail.com designates 10.52.95.108 as permitted sender) client-ip=10.52.95.108; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ryan.ramage@gmail.com designates 10.52.95.108 as permitted sender) smtp.mail=ryan.ramage@gmail.com; dkim=pass header.i=ryan.ramage@gmail.com Received: from mr.google.com ([10.52.95.108]) by 10.52.95.108 with SMTP id dj12mr13105366vdb.4.1329862969122 (num_hops = 1); Tue, 21 Feb 2012 14:22:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=cIdOTynUd/pGpen5zE5wgWFA+KCq7lUciqBXSBawmDw=; b=QnKN9IOd/jPSQ9FkaHXuOvWPMaV9mZ6QQBTQdh5STfYNHAgyBFxyLk9Pt3r1YxEH0T bOGqkrYGbyZcq3OwoPgJgP0A46uAxNiihCS/E5PRaoOJNr9GZto3tDAqvWKb1YkpCLp6 ZaeqEycgLqsc+40++ue57BU6nRTX2WxRUHUgc= MIME-Version: 1.0 Received: by 10.52.95.108 with SMTP id dj12mr10600257vdb.4.1329862968939; Tue, 21 Feb 2012 14:22:48 -0800 (PST) Received: by 10.220.152.134 with HTTP; Tue, 21 Feb 2012 14:22:48 -0800 (PST) In-Reply-To: <1329858735601-7306229.post@n2.nabble.com> References: <1329858735601-7306229.post@n2.nabble.com> Date: Tue, 21 Feb 2012 15:22:48 -0700 Message-ID: Subject: Re: General question about views From: Ryan Ramage To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable John, These question are typically handled in the users forum. But otherwise for generic queries you can use https://github.com/rnewson/couchdb-lucene. or elasticsearch http://www.elasticsearch.org/guide/reference/river/couchdb.html On Tue, Feb 21, 2012 at 2:12 PM, JohnRodey wrote: > I have some WebServices that act as a middle man between our client > applications and our backend repository(CouchDB). =A0I wanted to create a= nd > infrastructure where users could enter search criteria to a web service p= ost > and run a query on those fields and do so in a generic way that isnt vend= or > specific. =A0I would like my client to be able to do something similar to > "http://host:port/query?name=3D"bob",birthdatestart=3D"1980/07/04",birthd= ateend=3D"1981/07/04",hieght=3D"6'1""". > > I basically want the ability to handle any type of query that a user thro= ws > at me. =A0But as Im looking it seems like this isnt exactly how CouchDB w= as > built. =A0It seems like I would rather have a set of supported queries su= ch as > "http://host:port/query=3DfindByBirthdate?birthdatestart=3D"1980/07/04",b= irthdateend=3D"1981/07/04"". > Is this true? =A0I believe that I could accomplish what I want through > temporary views, but I know these are not desired for production. > > If I can somehow handle dynamic query parameters, is there a way to handl= e > which fields from the document to return to the user? > > Thanks for any insight! > > -- > View this message in context: http://couchdb-development.1959287.n2.nabbl= e.com/General-question-about-views-tp7306229p7306229.html > Sent from the CouchDB Development mailing list archive at Nabble.com.