4 ms·

Don't forget: 695 - Mongoid http://github.com/durran/mongoid http://github.com/durran/mongoid seems to be the Rails/Mongo project to watch. They got a slick l

by ruperp 16y ago

Don't forget: 695 - Mongoid http://github.com/durran/mongoid http://github.com/durran/mongoid seems to be the Rails/Mongo project to watch. They got a slick looking homepage too: http://mongoid.org http://mongoid.org Hoping to try using it on my next project.

ekidd 16y ago
We've used both MongoMapper and Mongoid, and are very happy with Mongoid. It has nice ActiveModel integration, so it works quite well with Rails 3.
- bkudria 16y ago
  Seconded, using Mongoid over MM here too. It rocks.
deleted 16y ago
[deleted]
mrinterweb 16y ago
Currently the choice between MongoMapper and Mongoid is pretty simple. If you're using Rails 2.3.x, MongoMapper. If you're using Rails 3, Mongoid. The ActiveModel integration is key for Rails 3. Mongoid also has great documentation. MongoMapper does not as much consolidated documentation.
spohlenz 16y ago
I'd also recommend checking out my MongoModel project, especially if you have been dissatisfied with the way MongoMapper or Mongoid do things. http://github.com/spohlenz/mongomodel http://github.com/spohlenz/mongomodel http://www.mongomodel.org http://www.mongomodel.org It's not quite as mature, but more documentation updates are currently in progress.
- jpcx01 16y ago
  Not sure I totally understand. But it looks like its just a rewrite of MongoMapper for Rails3? Seems like the structure is very similar. What didn't you like about MongoMapper and/or Mongoid? Starting from scratch is a big job.
  - spohlenz 16y ago
    Firstly, MongoModel was started back in November '09 when both MongoModel and and Mongoid were much less mature than they are now. I spent some time contributing patches to MongoMapper but stumbled as I was working on edge rails. MongoMapper in particular has come a long way since then but still has a few issues in my mind. For example, attributes are converted to/from their mongo representation every single time they are accessed, rather than only when the model is saved or loaded. I also believe MongoModel has a nicer model for typecasting property values (see http://gist.github.com/287379 http://gist.github.com/287379 for an example), and I disagree with the use of has_many associations for embedded collections. MongoModel isn't perfect either, but it has been the path of least resistance for me in getting my app running on MongoDB.
    - jpcx01 16y ago
      Cool, thanks for the explanation. Btw, mongoid has a new association dsl that I think makes way more sense. embedded_in, embeds_many, referenced_in, references_many. I bet the project would love to see you as a contributor.

by ruperp 16y ago

ekidd 16y ago

We've used both MongoMapper and Mongoid, and are very happy with Mongoid. It has nice ActiveModel integration, so it works quite well with Rails 3.

bkudria 16y ago
Seconded, using Mongoid over MM here too. It rocks.

deleted 16y ago

[deleted]

mrinterweb 16y ago

Currently the choice between MongoMapper and Mongoid is pretty simple. If you're using Rails 2.3.x, MongoMapper. If you're using Rails 3, Mongoid. The ActiveModel integration is key for Rails 3. Mongoid also has great documentation. MongoMapper does not as much consolidated documentation.

spohlenz 16y ago

I'd also recommend checking out my MongoModel project, especially if you have been dissatisfied with the way MongoMapper or Mongoid do things. http://github.com/spohlenz/mongomodel http://github.com/spohlenz/mongomodel http://www.mongomodel.org http://www.mongomodel.org It's not quite as mature, but more documentation updates are currently in progress.

jpcx01 16y ago
Not sure I totally understand. But it looks like its just a rewrite of MongoMapper for Rails3? Seems like the structure is very similar. What didn't you like about MongoMapper and/or Mongoid? Starting from scratch is a big job.
- spohlenz 16y ago
  Firstly, MongoModel was started back in November '09 when both MongoModel and and Mongoid were much less mature than they are now. I spent some time contributing patches to MongoMapper but stumbled as I was working on edge rails. MongoMapper in particular has come a long way since then but still has a few issues in my mind. For example, attributes are converted to/from their mongo representation every single time they are accessed, rather than only when the model is saved or loaded. I also believe MongoModel has a nicer model for typecasting property values (see http://gist.github.com/287379 http://gist.github.com/287379 for an example), and I disagree with the use of has_many associations for embedded collections. MongoModel isn't perfect either, but it has been the path of least resistance for me in getting my app running on MongoDB.
  - jpcx01 16y ago
    Cool, thanks for the explanation. Btw, mongoid has a new association dsl that I think makes way more sense. embedded_in, embeds_many, referenced_in, references_many. I bet the project would love to see you as a contributor.