StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14608316
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-01-30T16:02:04.963
FavoriteCount
0
LastActivityDate
2013-01-30T16:27:53.087
LastEditDate
2013-01-30T16:27:53.087
LastEditorUserId
426671
OwnerUserId
426671
ParentId
14608184
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The error that you were getting is because SQL Server requires any item in the <code>SELECT</code> list to be included in the <code>GROUP BY</code> if there is an aggregate function being used. The problem with that is you might have unique values in some columns which can throw off the result. So you will want to rewrite the query to use one of the following: You can use a subquery to get this result. This gets the <code>max(created)</code> in a subquery and then you use that result to get the correct employee record: <pre><code>select s.id SkillId, s.employee_id, s.competency_id, s.created, e.id employee, e.first_name, e.last_name, c.id competency, c.title from Employees e left join Skills s on e.id = s.employee_id inner join ( SELECT MAX(created) as created, employee_id FROM skills GROUP BY employee_id ) s1 on s.employee_id = s1.employee_id and s.created = s1.created left join Competencies c on s.competency_id = c.id </code></pre> See <a href="http://sqlfiddle.com/#!3/e2259/12" rel="nofollow">SQL Fiddle with Demo</a> Or another way to do this is to use <code>row_number()</code>: <pre><code>select * from ( select s.id SkillId, s.employee_id, s.competency_id, s.created, e.id employee, e.first_name, e.last_name, c.id competency, c.title, row_number() over(partition by s.employee_id order by s.created desc) rn from Employees e left join Skills s on e.id = s.employee_id left join Competencies c on s.competency_id = c.id ) src where rn = 1 </code></pre> See <a href="http://sqlfiddle.com/#!3/e2259/13" rel="nofollow">SQL Fiddle with Demo</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSQL Server Query using GROUP BY
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTaryn
UserOwnerUserId
1. USTaryn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSQL Server Query using GROUP BY
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COBoth of the queries worked. Thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USjoeljoeljoel
2. CO@joeljoeljoel you are welcome. :)
 singulars
 PostPostId
 PO
 UserUserId
 USTaryn

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.