Removes use of ObjectSpace from `rake db:create_indexes`
[resolves github issue #180]
…. Truth check copied from ActiveRecord
[Resolves github issue #205]
[Resolves github issue #175]
When setting the parent attribute on the child document we check whether the association is a references_many or referenced_in to decide if we need to push or set the id. [Resolves github issue #206]
Shell scripts exit when they encounter failures, and call `rake` instead of `rake spec`.
Since a references_many :stored_as => :array association stores the related object ids in an internal collection, setting the inverse association is optional. This allows for one-way referential associations.
…dler > 1.0.0.beta.1
By default this gets run if autocreate_indexes option is on. Otherwise you can run it manually (or use the rake db:create_indexes) to create the indexes on your MongoDB database
If Passenger or Unicorn are configured to load the application before forking their workers, we reconnect to mongo in the child process.
…llows for the syntax Address.near(:latlng => [37.7, -122.4, 1]).
Also added rake db:create_indexes that will force mongoid to create the indexes on your database (may take a long time). If you want the old functionality, just set autocreate_indexes to true (via yml, or direct config). The recommended behavior though is to keep this turned off, and create indexes manually via mongodb.
This reverts commit c999b1f.
They both do the same thing. Unless we're able to get separate loggers per model, I think its best to deprecate this one.
…s, cleaning up nested build on embeds many
…ection criteria. Moved deleted scope into Mongoid::Paranoia and deleted Mongoid::Paranoid.