StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19353371
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-10-14T04:03:33.967
FavoriteCount
0
LastActivityDate
2013-10-14T04:03:33.967
LastEditDate
LastEditorUserId
0
OwnerUserId
494204
ParentId
19349715
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
First I would recommend start separating your Rails concepts from Ember. MVC means different things both in Ember and Rails, as Rails developer I also try to look for analogies and sometimes can get confusing (I'm working on a simple community guide for Rails devs into Ember <a href="https://github.com/abuiles/ember-rails-style-guide" rel="nofollow">https://github.com/abuiles/ember-rails-style-guide</a>) In Ember, the way to keep those "semantic methods" is done with Routes. In your case you'd have the OrdersIndexRoute, OrdersNewRoute, OrdersEditRoute (think of each of this ones as the "actions" in Rails) where OrdersIndexRoute = index action, you will need to setup all your orders models to be listed. It will look something like <pre><code>App.OrdersIndexRoute = Ember.Route.Extend({ model: function(){ return Order.all; // If you are using ember-data this would be different, just supposing Orders.all returns all your orders models. } }); </code></pre> OrdersNewRoute = new action, you will need to setup a <code>new</code> object which will be bound to the form and then submitted to your server. <pre><code>App.OrdersNewRoute = Ember.Route.Extend({ model: function(params){ return Order.new() // returns a new instance of your model }, actions: { // this means that you would have something in your template like <button {{action this}}>... save: function(model){ model.save() } } }); </code></pre> OrdersEditRoute = edit action, the <code>model</code> here would be the one that you want to edit. <pre><code>App.OrdersEditRoute = Ember.Route.Extend({ model: function(params){ return Order.find(params.id) }, actions: { save: function(model){ model.save() } } }); </code></pre> When you have this kind of doubt, feel free to jump into #emberjs in IRC, lots of smart and helpful fools there, willing to give you a hand when need it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POember 1.0.0 semantic commands in controller or own routes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAdolfo Builes
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POember 1.0.0 semantic commands in controller or own routes
 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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.