Book Image

Learning Mongoid

By : Gautam Rege
Book Image

Learning Mongoid

By: Gautam Rege

Overview of this book

Mongoid helps you to leverage the power of schema-less and efficient document-based design, dynamic queries, and atomic modifier operations. Mongoid eases the work of Ruby developers while they are working on complex frameworks. Starting with why and how you should use Mongoid, this book covers the various components of Mongoid. It then delves deeper into the detail of queries and relations, and you will learn some tips and tricks on improving performance. With this book, you will be able to build robust and large-scale web applications with Mongoid and Rails. Starting with the basics, this book introduces you to components such as moped and origin, and how information is managed, learn about the various datatypes, embedded documents, arrays, and hashes. You will learn how a document is stored and manipulated with callbacks, validations, and even atomic updates. This book will then show you the querying mechanism in detail, right from simple to complex queries, and even explains eager loading, lazy evaluation, and chaining of queries. Finally, this book will explain the importance of performance tuning and how to use the right indexes. It also explains MapReduce and the Aggregation Framework.
Table of Contents (14 chapters)
Learning Mongoid
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

has_one – the one-to-one relation


As the method name suggests, has_one sets up the parent relation for a model having only one child:

class Book
  include Mongoid::Document

  has_one :book_detail
end

This implies that "A Book class has one BookDetail". For every parent relation, it is advisable to set the child relationship too.

class BookDetail
  include Mongoid::Document

  belongs_to :book
end

The has_one method takes the options discussed in the following sections.

:as

When a relation is a polymorphic relation, we need to use this option:

class Ship
  include Mongoid::Document  

  has_one :vehicle, as: resource
end

This tells the has_one method that the vehicle is a polymorphic relation that can be accessed via the resource_type and resource_id fields in the vehicles collection. It's important that the inverse relation sets polymorphic: true, and we will see polymorphic relations soon.

:autosave

The :autosave option is false by default. When the object is created, the related child objects...