ruby_class attribute in every document about couch_potato

[langalex]

without the ruby_class we don't know which class to use when converting the document into a ruby object. also, you can't do things like finding all blog posts without knowing wether a particular document is a blog post or not.

[shenoudab]

but what if every database have only one Model. as say that this database have documents which represent "Post" Model.
so when converting to Ruby Object i know that i will convert them to Post Model.
and also finding Posts, as every document in that database is represent a Post Model ....

[langalex]

do you have any specific reason to put every kind of document into a separate database? if not you might find your mindset stuck in SQL land... anyway if you have reasons to do so, then you can overwrite the to_hash method in CouchPotato and filter out the ruby_class attribute.

[shenoudab]

thanks for your support ... as i will have a database to represent one Model.. the core model.

but i'd like to ask .. is overwriting the to_hash method ... will not write the "ruby_class" in the document and also the dynamic views ..

[langalex]

i don't know what you are talking about, can you rephrase your question?

[shenoudab]

sorry, i'd like to ask how to ignore write the ruby_class property in the document.
and also ignore represent the ruby_class in dynamic views offered by couch_potato.

is overwriting to_hash method will cover the above.

[langalex]

def to_hash
  hash = super.dup
  hash.delete('ruby_class')
  hash
end

the auto generated view all check for the ruby_class, so you have to provide your own map function:

view :my_view, :type => :custom, :map => "function(doc) {emit(...)}"