I have some WebServices that act as a middle man between our client applications and our backend repository(CouchDB). I wanted to create and infrastructure where users could enter search criteria to a web service post and run a query on those fields and do so in a generic way that isnt vendor specific. I would like my client to be able to do something similar to "http://host:port/query?name="bob",birthdatestart="1980/07/04",birthdateend="1981/07/04",hieght="6'1""".
I basically want the ability to handle any type of query that a user throws at me. But as Im looking it seems like this isnt exactly how CouchDB was built. It seems like I would rather have a set of supported queries such as "http://host:port/query=findByBirthdate?birthdatestart="1980/07/04",birthdateend="1981/07/04"";. Is this true? I 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 handle which fields from the document to return to the user? Thanks for any insight! -- View this message in context: http://couchdb-development.1959287.n2.nabble.com/General-question-about-views-tp7306229p7306229.html Sent from the CouchDB Development mailing list archive at Nabble.com.
