StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19942265
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-12T23:37:23.927
FavoriteCount
0
LastActivityDate
2013-11-12T23:44:03.757
LastEditDate
2013-11-12T23:44:03.757
LastEditorUserId
1939604
OwnerUserId
1939604
ParentId
19941919
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>In my point of view, all your logic should be placed in your controller, models, helpers or libraries. In your case, setting variables should be done in your controller and not in your views.</p> <p>It's really interresting to place your logic at the good place, because it will be more easy to debug, maintain or refactore your application if your code is at the good place.</p> <p>So, here are some ideas to put your variables declarations in your controller without duplicate your code :)</p> <h2>before_action (in controller)</h2> <p>You can use <code>before_action</code> in your controller. It will reduce the duplicated code.</p> <p>For example, you can do:</p> <pre><code>before_action :set_variables def set_variables @var1 = some_code @var2 = other_code ... end </code></pre> <p>You can restrict the before_action to only specific actions by using <code>only</code> or <code>except</code></p> <pre><code>before_action :set_variables, only: [:index, :edit] </code></pre> <p>This will call set_variables only before index and edit</p> <h2>before_action (in application_controller.rb)</h2> <p>If you want to add a before_action for all index actions in every controllers for examples, you just have to do a before_action in your application_controller.rb</p> <p>And if you want to skip this type of before_action in a specific controller, you can use the skip_before_action method.</p> <pre><code># application_controller.rb before_action :set_variables, only: :index # specific_controller.rb skip_before_action :set_variables </code></pre> <h2>One more thing: model scopes</h2> <p>Then, a last thing before the end: <code>Model1.where(some conditions)</code>. What about model scopes?</p> <p>Your code will be more readable and less duplicated:</p> <pre><code>class MyModel < ActiveRecord::Base scope :active, -> { where(is_active: true) } end MyModel.active # equivalent to MyModel.where(is_active: true) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs it bad to have fat views in rails?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSimon Ninon
UserOwnerUserId
1. USSimon Ninon
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
3. 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.