StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14682163
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2013-02-04T07:29:30.527
FavoriteCount
0
LastActivityDate
2013-02-04T08:58:46.523
LastEditDate
2013-02-04T08:58:46.523
LastEditorUserId
491243
OwnerUserId
491243
ParentId
14682104
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code>SELECT b.`name Item`, a.qty `Sold Quantity`, a.price `@ price`, (a.qty * a.price) Total FROM transaction_detail a INNER JOIN Item b ON a.idItem = b.idItem </code></pre> <ul> <li><a href="http://www.sqlfiddle.com/#!2/f7090/2" rel="nofollow">SQLFiddle Demo</a></li> </ul> The query above is based on the records and result given on the example. Follow-up question(s): is there any possibility that a certain Item can be sold with different price? If so, how do you calculate it? UPDATE 1 <pre><code>SELECT b.`name Item`, SUM(a.qty) `Sold Quantity`, a.price `@ price`, (SUM(a.qty) * a.price) Total, c.Date FROM transaction_detail a INNER JOIN Item b ON a.idItem = b.idItem INNER JOIN `transaction` c ON a.idtransaction = c.idTransaction GROUP BY b.idItem, b.`name Item`, a.price, c.Date </code></pre> <ul> <li><a href="http://www.sqlfiddle.com/#!2/ab120/4" rel="nofollow">SQLFiddle Demo</a></li> </ul> UPDATE 2 <pre><code>SELECT b.`name Item`, SUM(a.qty) `Sold Quantity`, a.price `@ price`, (SUM(a.qty) * a.price) Total, d.`Name Customer` FROM transaction_detail a INNER JOIN Item b ON a.idItem = b.idItem INNER JOIN `transaction` c ON a.idtransaction = c.idTransaction INNER JOIN Customer d ON d.idCustomer = c.idCustomer GROUP BY b.idItem, b.`name Item`, a.price, MONTH(c.Date), YEAR(c.Date), d.`Name Customer` </code></pre> <ul> <li><a href="http://www.sqlfiddle.com/#!2/5d648/2" rel="nofollow">SQLFiddle Demo</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmysql item sales
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJohn Woo
UserOwnerUserId
1. USJohn Woo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POmysql item sales
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.