StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11514161
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-16T23:41:20.537
FavoriteCount
0
LastActivityDate
2012-07-16T23:41:20.537
LastEditDate
LastEditorUserId
0
OwnerUserId
689692
ParentId
10913998
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I should have posted my solution a while back - there might well be a better way, but this is the convention I've gone with: All of the following code is in the card view (which is where the notes are displayed). First, I bind a <code>renderNotes</code> method to the <code>'reset'</code> event on the card's notes collection: <pre><code>initialize: function () { _.bindAll(this); this.model.get('notes').on('reset', this.renderNotes); var self = this; this.model.get('notes').on('add', function(addedNote, relatedCollection) { self.renderNote(addedNote); }); } </code></pre> I also bind to the <code>'add'</code> on that collection to call a singular <code>renderNote</code>. The renderNotes and renderNote methods work like this: <pre><code>renderNotes: function () { if (this.model.get('notes')) { this.model.get('notes').each(this.renderNote); } }, renderNote: function (note) { var noteView = new Workflow.Views.Note({ model: note }); this.$('.notes').append(noteView.render().el); }, </code></pre> Then, the last piece of the puzzle is to actually hit the server up for the card's notes (which will in turn fire the <code>'reset'</code> event I bound to above). I do this in the card view's <code>render</code> method: <pre><code>render: function () { // render all of the eager-loaded things this.model.get('notes').fetch(); return this; }, </code></pre> As @user1248256 kindly helped me work out in the comments on my OP, the confusion was mainly in that I expected <code>fetchRelated</code> to pull down lazy-loaded records - that's actually not the case. As a side-note, this view is actually a modal and be opened and closed (removed from the page). To prevent the zombie events problem described in <a href="http://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CFEQFjAA&url=http://lostechies.com/derickbailey/2011/09/15/zombies-run-managing-page-transitions-in-backbone-apps/&ei=Up8EULXmBe7omAXmm_2kBg&usg=AFQjCNEP8_EpNm9a5ygpvsRfviq-izWdIA&sig2=xXQ3eYohyrSSZ0rrhYz8jQ" rel="nofollow">this excellent post</a>, I also manually unbind the events mentioned above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBackbone-relational fetchRelated not sending request
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USStu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBackbone-relational fetchRelated not sending request
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.