StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3007798
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-09T16:27:16.150
FavoriteCount
0
LastActivityDate
2010-06-09T16:42:29.950
LastEditDate
2010-06-09T16:42:29.950
LastEditorUserId
175836
OwnerUserId
175836
ParentId
3007285
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If you would like to handle this on the Rails stack itself, one way I currently handle a similar situation is using an ActiveRecord Callback method. Documentation for that is available <a href="http://api.rubyonrails.org/classes/ActiveRecord/Callbacks.html#M001381" rel="nofollow noreferrer">here</a>. In your model where the attribute is originally being modified you could use the after_validation_on_create callback: <pre><code>after_validation_on_create :toggle_other_table_asset def toggle_other_table_asset if self.in_use sibling.in_use = 1 else sibling.in_use = 0 end sibling.save end </code></pre> You also might want to consider using an ActiveRecord transaction to ensure the integrity of your data, more information is found <a href="http://api.rubyonrails.org/classes/ActiveRecord/Transactions/ClassMethods.html" rel="nofollow noreferrer">here</a>. The best piece of advice I can give you is to consider the potential drawbacks to ensuring everything is done on the application layer. There's also drawbacks involved in coupling your data in this fashion. Perhaps you should think about refactoring your models to avoid duplication of data. Examples of where things can go wrong include maintenance scripts which run on the weekends that clean up your database, or interacting with your underlying database's command line interface and modifying the culprit attributes manually.. without having a database TRIGGER programmed, you're running the risk of damaging the integrity of your data.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I connect two DB tables using Rails?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USrandombits
UserOwnerUserId
1. USrandombits
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow can I connect two DB tables using Rails?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.