Ability to send explicit null as key?
Reported by hkstar | November 22nd, 2008 @ 07:56 PM
CouchDB often relies on an explicit "null" as a key in a view request. Currently, I can't see any way to duplicate this in CouchRest::Model. It's especially important in startkey/endkey requests as the "opposite" of {}.
Am I missing something, or is this something I need to add myself?
Thanks. And sorry, dev, for the flood of tickets.
Comments and changes to this ticket
-
J. Chris A. November 23rd, 2008 @ 10:02 AM
- State changed from “new” to “resolved”
I think Ruby's nil will work just fine, when you want JSON null.
-
hkstar November 23rd, 2008 @ 12:38 PM
OK, cool, if that's the "official" way to do it. Thanks for the clarification.
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.
hkstar
J. Chris A.