StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12270938
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-04T20:32:19.047
FavoriteCount
0
LastActivityDate
2012-09-04T20:32:19.047
LastEditDate
LastEditorUserId
0
OwnerUserId
295228
ParentId
12269487
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I think you should rebuild this associations and models What I'd do is to have this models (a little bit different than yours): Salesman <pre><code>class Salesman < ActiveRecord::Base attr_accessible :last_name, :name has_many :sales end </code></pre> Product <pre><code>class Product < ActiveRecord::Base attr_accessible :name, :qty has_many :product_sales end </code></pre> Sale <pre><code>class Sale < ActiveRecord::Base belongs_to :salesman has_many :product_sales end </code></pre> And here's the trick Model ProductSale <pre><code>class ProductSale < ActiveRecord::Base belongs_to :sale belongs_to :product attr_accessible :qty after_create :decrement_stock def decrement_stock self.product.update_attribute("qty", (product.qty - self.qty)) end end </code></pre> There you have Sale that <code>belongs_to</code> salesman. Sale <code>has_many</code> <code>product_sales</code> and <code>product_sales</code> belongs_to <code>product</code> and <code>sales</code> that way in one sale you have multiple product Then when a <code>ProductSale</code> is saved there's the callback <code>after_create :decrement_stock</code> And you can update the attribute for that specific product. Remember that you'll have a quantity for each product and not for the whole sale. Here's a little example I set up for you: <a href="https://github.com/Mr-Nizzle/inventory" rel="nofollow">https://github.com/Mr-Nizzle/inventory</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails: decrement attribute in table when other record is created
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMr_Nizzle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails: decrement attribute in table when other record is created
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COEres el mejor :') Mis respetos...
 singulars
 PostPostId
 PO
 UserUserId
 USJmlevick

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.