StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1649675
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2009-10-30T12:56:17.033
FavoriteCount
0
LastActivityDate
2009-10-30T13:05:03.007
LastEditDate
2009-10-30T13:05:03.007
LastEditorUserId
8985
OwnerUserId
8985
ParentId
1648971
PostTypeId
2
Score
33
ViewCount
0
LastEditorDisplayName
text
Body
Avoid <code>default_scope</code> if possible. I think you should really re-ask yourself why you need a <code>default_scope</code>. Countering a <code>default_scope</code> is often messier than it's worth and it should only be used in rare cases. Also, using <code>default_scope</code> isn't very revealing when ticket associations are accessed outside the Ticket model (e.g. "I called <code>account.tickets</code>. Why aren't my tickets there?"). This is part of the reason why <code>with_exclusive_scope</code> is protected. You should taste some <a href="http://www.loudthinking.com/arc/2006_10.html" rel="noreferrer">syntactic vinegar</a> when you need to use it. As an alternative, use a gem/plugin like <a href="http://github.com/thoughtbot/pacecar" rel="noreferrer">pacecar</a> that automatically adds useful named_scopes to your models giving you more revealing code everywhere. For Example: <pre><code>class Ticket < ActiveRecord::Base include Pacecar belongs_to :user end user.tickets.ends_at_in_future # returns all future tickets for the user user.tickets # returns all tickets for the user </code></pre> You can also decorate your User model to make the above code cleaner: <pre><code>Class User < ActiveRecord::Base has_many :tickets def future_tickets tickets.ends_at_in_future end end user.future_tickets # returns all future tickets for the user user.tickets # returns all tickets for the user </code></pre> Side Note: Also, consider using a more idiomatic datetime column name like <code>ends_at</code> instead of <code>end_date</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails: Why is with_exclusive_scope protected? Any good practice on how to use it?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRyan McGeary
UserOwnerUserId
1. USRyan McGeary
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. COthx, yeah I know default_scope is evil, but in my specific case, which is a bit more complex as the given one, this is best solution (for now)
 singulars
 PostPostId
 PO
 UserUserId
 USRngTng

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.