StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9342159
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-18T14:44:56.637
FavoriteCount
0
LastActivityDate
2012-02-18T14:44:56.637
LastEditDate
LastEditorUserId
0
OwnerUserId
650800
ParentId
9339151
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I don't see too much business logic in your actions. Generally your controllers/actions role is to be a gateway for your domain model and services, and handle protocol specific stuff. CLI commands deals with command line arguments, controllers with HTTP requests, so your action methods do what they supposed to. You have a lot of options to refactor your code to eliminate these kind of duplicate codes in your controller actions using some refactoring patterns. <a href="http://martinfowler.com/refactoring/catalog/extractMethod.html" rel="nofollow">Extract method</a> to move these lines into a protected method of your controller. You can <a href="http://martinfowler.com/refactoring/catalog/extractSuperclass.html" rel="nofollow">extract a base class</a> for these similar controllers and move the methods there. In more complicated scenarios you can move controller logic (extracting domain specific information from the HTTP request) into services, especially if you need some other DIC managed services to complete this task. There is nothing wrong accessing the request object in these services. You can make this kind of services request scoped, or implement ContainerAware and get the request from the container. <pre class="lang-xml prettyprint-override"><code><service id="controller-helper-service" class="%helper.class%" scope="request"> <argument type="service" id="request" /> <argument type="service" id="some-other-service" /> </service> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSymfony2: How do I Reduce the Amount of Duplicate Logic in My Controller and Stick With the Thin Controller Fat Model Approach?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBártfai Tamás
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
2. 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.