I came across StrokeDB in comparing ThruDB and CouchDB, it seems
interesting but the API is quite awkward. Is the current Meta/Document
API in development or fixed? Is there any interest in making this into
something closer to some of the ORM's out there like ActiveRecord and
DataMapper? This may ease in others adopting it.

I'm personally partial to the DataMapper/merb pattern of using mixins,
something like:

class Blog
  include StrokeDB::Meta
end

rather than the current Blog = Meta.new, I think this is a cleaner
abstraction, models should be classes anyway IMHO.

Any ideas/feedback? I'm willing to spend some time doing a fork of the
git repo and implementing a cleaner user level API.

On Apr 22, 2008, at 3:54 PM, Paul Dlug wrote:

StrokeDB is in development, so any API might be changed eventually if  
there is enough reasons to.

Our Document API is pretty much close to ActiveRecord I believe, to  
the extent reasonable (since StrokeDB is not an ORM).

Also I should note that we had some discussions on IRC about adding  
StrokeDB support for DM (even though I hardly understand purpose of  
it, except for transferring legacy data)

Who said models should be classes anyway? StrokeDB provides a concept  
of multi-meta documents, i.e. documents that may have more than one  
meta document associated. This concept is way more close to real  
world, where every object can be seen from different points of views,  
in different aspects.

StrokeDB mixins meta modules into documents, and that is why  
StrokeDB's metas are modules — because there is no way to mix class in.

You are always welcome to contribute!

Yurii.