StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15210073
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-04T20:01:19.777
FavoriteCount
0
LastActivityDate
2013-03-04T20:57:36.037
LastEditDate
2013-03-04T20:57:36.037
LastEditorUserId
2133261
OwnerUserId
2133261
ParentId
11327390
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
EDIT: assuming that the association is not optional... The only way I can get it to thoroughly validate is this: <pre><code>validates_associated :project validates_presence_of :project_id, :unless => Proc.new {|o| o.project.try(:new_record?)} validates_presence_of :project, :if => Proc.new {|o| o.project_id} </code></pre> The first line validates whether the associated Project is valid, if there is one. The second line insists on the <code>project_id</code> being present, unless the associated Project exists and is new (if it's a new record, it won't have an ID yet). The third line ensures that the Project is present if there is an ID present, i.e., if the associated Project has already been saved. ActiveRecord will assign a <code>project_id</code> to the task if you assign a saved Project to <code>project</code>. If you assign an unsaved/new Project to <code>project</code>, it will leave <code>project_id</code> blank. Thus, we want to ensure that <code>project_id</code> is present, but only when dealing with a saved Project; this is accomplished in line two above. Conversely, if you assign a number to <code>project_id</code> that represents a real Project, ActiveRecord will fill in <code>project</code> with the corresponding Project object. But if the ID you assigned is bogus, it will leave <code>project</code> as nil. Thus line three above, which ensures that we have a <code>project</code> if <code>project_id</code> is filled in -- if you supply a bogus ID, this will fail. See RSpec examples that test these validations: <a href="https://gist.github.com/kianw/5085085" rel="nofollow">https://gist.github.com/kianw/5085085</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POThe perfect way to validate and test Rails 3 associations (using RSpec/Remarkable)?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKian Wright
UserOwnerUserId
1. USKian Wright
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.