Doing the simple stuff so you don't have to
Go to file
Adam Jacob c3e34fc989 Adding a Gem Package rake (rake package) task, along with rake install (to install the gem after building) 2009-03-27 11:52:04 -07:00
examples removed CouchRest::Model, added more specs and fixed a bug with casted CR::ExtendedDocument 2009-02-24 22:51:13 -08:00
lib bumped release to 0.23 (lots of fixes) 2009-03-27 11:27:44 -07:00
spec Make design_doc non-inheritable. Fixes bug where views added to a child class were propagated to the parent and siblings. Child class "all" view map function now checks in guard clause for child class name instead of parent name 2009-03-27 10:35:18 -07:00
utils s/localhost/127.0.0.1/ 2008-12-14 12:05:02 +01:00
.gitignore added gem task for easy local packaging 2008-10-26 10:03:59 -05:00
LICENSE added apache license 2008-09-11 21:31:59 -07:00
README.md removed CouchRest::Model, added more specs and fixed a bug with casted CR::ExtendedDocument 2009-02-24 22:51:13 -08:00
Rakefile Adding a Gem Package rake (rake package) task, along with rake install (to install the gem after building) 2009-03-27 11:52:04 -07:00
THANKS.md updated thanks file 2009-01-12 21:10:00 -08:00
couchrest.gemspec upgraded the gemspec (ruby1.9 compatible and enforcing a properly working version of rubygems) 2009-03-25 00:00:42 -07:00
github_gemtest.rb a file to check the gem build 2008-11-26 13:42:27 -08:00
make-gemspec.sh make gemspec cleans build products before gemspecing 2009-01-12 21:19:02 -08:00

README.md

CouchRest: CouchDB, close to the metal

CouchRest is based on CouchDB's couch.js test library, which I find to be concise, clear, and well designed. CouchRest lightly wraps CouchDB's HTTP API, managing JSON serialization, and remembering the URI-paths to CouchDB's API endpoints so you don't have to.

CouchRest is designed to make a simple base for application and framework-specific object oriented APIs. CouchRest is Object-Mapper agnostic, the parsed JSON it returns from CouchDB shows up as subclasses of Ruby's Hash. Naked JSON, just as it was mean to be.

Easy Install

Easy Install is moving to RubyForge, heads up for the gem.

Relax, it's RESTful

The core of Couchrest is Herokus excellent REST Client Ruby HTTP wrapper. REST Client takes all the nastyness of Net::HTTP and gives is a pretty face, while still giving you more control than Open-URI. I recommend it anytime youre interfacing with a well-defined web service.

Running the Specs

The most complete documentation is the spec/ directory. To validate your CouchRest install, from the project root directory run rake, or autotest (requires RSpec and optionally ZenTest for autotest support).

Examples

Quick Start:

# with !, it creates the database if it doesn't already exist
@db = CouchRest.database!("http://127.0.0.1:5984/couchrest-test")
response = @db.save_doc({:key => 'value', 'another key' => 'another value'})
doc = @db.get(response['id'])
puts doc.inspect

Bulk Save:

@db.bulk_save([
    {"wild" => "and random"},
    {"mild" => "yet local"},
    {"another" => ["set","of","keys"]}
  ])
# returns ids and revs of the current docs
puts @db.documents.inspect 

Creating and Querying Views:

@db.save_doc({
  "_id" => "_design/first", 
  :views => {
    :test => {
      :map => "function(doc){for(var w in doc){ if(!w.match(/^_/))emit(w,doc[w])}}"
      }
    }
  })
puts @db.view('first/test')['rows'].inspect 

CouchRest::Model

CouchRest::Model has been deprecated and replaced by CouchRest::ExtendedDocument

CouchRest::ExtendedDocument

Callbacks

CouchRest::ExtendedDocuments instances have 2 callbacks already defined for you: create_callback, save_callback, update_callback and destroy_callback

In your document inherits from CouchRest::ExtendedDocument, define your callback as follows:

save_callback :before, :generate_slug_from_name

CouchRest uses a mixin you can find in lib/mixins/callbacks which is extracted from Rails 3, here are some simple usage examples:

save_callback :before, :before_method
save_callback :after,  :after_method, :if => :condition
save_callback :around {|r| stuff; yield; stuff }

Check the mixin or the ExtendedDocument class to see how to implement your own callbacks.

Casting

Often, you will want to store multiple objects within a document, to be able to retrieve your objects when you load the document, you can define some casting rules.

property :casted_attribute, :cast_as => 'WithCastedModelMixin'
property :keywords,         :cast_as => ["String"]

If you want to cast an array of instances from a specific Class, use the trick shown above ["ClassName"]