StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19398045
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-16T07:59:36.633
FavoriteCount
0
LastActivityDate
2013-10-16T08:24:11.590
LastEditDate
2013-10-16T08:24:11.590
LastEditorUserId
584552
OwnerUserId
584552
ParentId
19397756
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Performance is not related to your arguments; they are about project organization. <blockquote> Maximum part of the business logic are moved to helper </blockquote> This shouldn't happen, you should move the business (aka models) logic inside the models. Rails doesn't force you doing it, so keeping the logic organization is up to developers. <blockquote> Models are used only for validation </blockquote> This is a consequence of putting the business (aka models) logic outside the models. You should move it from the controllers/helpers to the models. Again, Rails doesn't force you to do that, so it's up to developers to do it. <blockquote> Included all helper files in a module under lib directory and included that module in application controller. In many methods, no argument passed, instead they used the instance variable(create instance variable in calling method and use that instance variable in the called method). Each action will call a helper method to execute business logic and that method will call some other helper methods. All method are written as public, No protected and private method. </blockquote> I think that these points are (some more, some less) related to the Rails Helper design. One flaw of Rails is the Helper design: they go against the OO pattern and usually end up by being a bunch of unorganized functions, à la PHP. For this reason some people use Decorators. Decorators "add an OO layer of presentation logic" (from <a href="https://github.com/drapergem/draper" rel="nofollow">Draper</a>), allowing to organize better the view related methods. If you want to examine the argument, I suggest you the following links: <ul> <li><a href="https://www.google.com/search?q=rails+decorator" rel="nofollow">Google search about decorators</a></li> <li><a href="https://github.com/drapergem/draper" rel="nofollow">Draper</a></li> <li><a href="https://www.ruby-toolbox.com/categories/rails_presenters" rel="nofollow">The Ruby Toolbox, presenters category</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POrails coding conventions to improve performance
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmdesantis
UserOwnerUserId
1. USmdesantis
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.