StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7262132
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-31T19:09:57.083
FavoriteCount
0
LastActivityDate
2011-09-02T21:48:55.263
LastEditDate
2011-09-02T21:48:55.263
LastEditorUserId
479167
OwnerUserId
333880
ParentId
7241524
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
There are several options you have. Here are a couple things to keep in mind: <ul> <li>Mongoid has a versioning plugin where you can keep track of versions of a document</li> <li>You can create an embedded document to store notes/changes on a model. Use an observer to add a note when certain things happen. You can tie this note to the document version if you'd like.</li> </ul> I have a case where I'm using an embedded Note object to track the state and progression of an order. Here's a rough outline of what I did: <pre><code>class Order include Mongoid::Document include Mongoid::Paranoia include Mongoid::Timestamps embeds_many :notes, as: :notable # fields end class Note include Mongoid::Document include Mongoid::Timestamps field :message field :state field :author #(I can add notes to any Model through :notable) embedded_in :notable, polymorphic: true end </code></pre> Then I created an observer to track state changes in Order: <pre><code>class OrderObserver < Mongoid::Observer def after_transition(order, transition) order.notes.build(state: transition.to) end end </code></pre> <code>after_transition</code> is a callback that the state machine plugin provides. If you don't care about integrating a state machine, you can just use Mongoid-provided callbacks like <code>after_save</code>, <code>after_update</code>, <code>around_update</code>, etc. Each time I transition through the states of an Order, I get a new timestamped note that records the history of each transition. I've left a lot of implementation details out, but it's working well for me so far. Links: <ul> <li><a href="http://mongoid.org/docs/extras.html" rel="nofollow">mongoid extras</a></li> <li><a href="http://github.com/pluginaweek/state_machine" rel="nofollow">state_machine</a></li> <li><a href="http://mongoid.org/docs/callbacks/observers.html" rel="nofollow">mongoid observers</a> - what callbacks Mongoid provides for Observers</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do you track history & activity with Mongoid?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USrubish
UserOwnerUserId
1. USJT.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.