Avoid unnecessary PUT requests
Reported by richmorin | February 13th, 2009 @ 09:41 AM
CR generates a PUT request whenever an app starts up, if the app defines a view. This creates work for the database (and possibly, monitoring programs) which is avoidable in many cases.
It would be better for CR to GET the view first. If the old view exists and is the same as the new view (the common case), CR could avoid doing the PUT request.
In my own (admittedly odd) application, there is another reason to want this behavior. I am writing a proxy that will prevent all requests (eg, PUT, DELETE) that could modify the database. CR's current behavior makes this impossible, short of monkey-patching.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
"CouchDB, close to the metal." <a href="http://github.com/jchris/couchrest/tree/master">CouchRest</a> is a RESTful layer for accessing CouchDB, based off CouchDB's included Javascript reference client. CouchRest also includes helpers for running large queries etc. There is also a base class for ActiveRecord / Datamapper style ORM, called CouchRest::Model.
J. Chris A.
richmorin