Comments on: A CouchDB primer for an ActiveRecord mindset

By: CouchDb docs, tutorials, link, blogs « Aler Diary

CouchDb docs, tutorials, link, blogs « Aler Diary — Wed, 07 Jan 2009 21:58:58 +0000

[...] CouchDb for an ActiveRecord mindset [...]

By: Charlie

Charlie — Mon, 05 Jan 2009 12:28:19 +0000

I know that by default CouchDB uses javascript for its map and reduce functions that generate its views, but that this is implemented as a separate module and is therefore entirely replaceable by any other language.

It seems to me that if one wants to define these functions within a project to keep them version controlled and bundled together with the rest of the application (seems reasonable), one might as well directly write the functions directly rather than, say writing a ruby thingy that generates the javascript view functions.

Better to use the full power of CouchDB’s MapReduce implementation (which, as an aside, and as has been noted elsewhere, might better be named “MapCombine” to distinguish it from the flavor described in the MapReduce whitepaper, the difference being that CouchDB requires Reduce functions to be commutative and associative so they can be sliced, diced, memoized and combined) and write your map and reduce functions directly.

Either javascript or ruby would be reasonable choices for a rails or merb project, it seems to be. Either way, I wouldn’t bother to translate it since CouchDB can use pretty much any language natively for this task.

By: Markus

Markus — Tue, 11 Nov 2008 22:18:11 +0000

Vodka bottles would be nice too! It looks nice

By: Couch Potato unleashed - a couchdb persistence layer in ruby | upstream agile - software

Mon, 27 Oct 2008 09:52:01 +0000

[...] Potato on github now. For an introduction to CouchDB and ruby please read my previous blog post A CouchDB primer for an ActiveRecord mindset. The following is a very short introduction into using Couch Potato. If you want to know more you [...]

By: เร็วส์ หกสิบหก » นั่งเทียนเขียนข่าว#12

เร็วส์ หกสิบหก » นั่งเทียนเขียนข่าว#12 — Thu, 02 Oct 2008 21:21:01 +0000

[...] A CouchDB primer for an ActiveRecord mindset | upstream agile - software [...]

By: Alexander Lang

Alexander Lang — Fri, 26 Sep 2008 08:21:50 +0000

@vity that’ll be a 2.0 feature

By: Vity

Vity — Thu, 25 Sep 2008 21:31:09 +0000

If you use submodules you should call them chips

…sorry

By: AndrewO

AndrewO — Thu, 25 Sep 2008 14:28:49 +0000

> damnit, i’m just reading on wikipedia that “Potatoe” is actually considered incorrectly spelled and it should be “Potato”

And all thought time I thought you were just making a Dan Quayle joke! That probably would have been a little dated though…

By: Alexander Lang

Alexander Lang — Thu, 25 Sep 2008 13:58:46 +0000

hey there,

sorry i had actually planned to include couchobject into the talk but ran out of time.

yeah, not having an additional generic layer is definitely an option i’m considering. but then again i’m hoping to maybe gather some new ideas simply by playing around with things. we’ll see how it goes. there must be something worth improving, somewhere

By: Johan S

Johan S — Thu, 25 Sep 2008 13:37:03 +0000

Your approach sounds very similar to my CouchObject library (http://gitorious.org/projects/couchobject), it even has a module called Persistable and inlined/external has_many’s.

However, and this is quite interesting, after working with couchdb some more I’ve sort of come to the conclusion that it’s still not the “right” way to interact with it. I think couchrest gets a lot more right by being minimal up front and letting your domain objects just use a repository-like pattern to retrieve the actual data from the hash, because really, that’s what it is in couchdb; a hash. Or document, if you will.
And then you can take it from there to make it more specific to whatever way you prefer to build apps. Don’t look at activerecord for inspiration, you won’t find much (other than maybe the abstract domain things, like validation, but there’s a validatable gem for that)