StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7837531
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-20T14:32:13.140
FavoriteCount
0
LastActivityDate
2011-10-20T14:38:45.300
LastEditDate
2017-05-23T12:27:33.637
LastEditorUserId
-1
OwnerUserId
411022
ParentId
7832806
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Regarding filtering on tags (which you mentioned in the comments on <a href="https://stackoverflow.com/questions/7832806/optimising-mysql-query-on-joined-tables-with-group-by-and-order-by-without-using/7833628#7833628">Johan's answer</a>), if the obvious <pre><code>SELECT p.*, GROUP_CONCAT(pt.name) AS tags FROM products p JOIN product_tags_for_products pt4p2 ON (pt4p2.product_id = p.id) JOIN product_tags pt2 ON (pt2.id = pt4p2.product_tag_id) LEFT JOIN product_tags_for_products pt4p ON (pt4p.product_id = p.id) LEFT JOIN product_tags pt ON (pt.id = pt4p.product_tag_id) WHERE pt2.name IN ('some', 'tags', 'here') GROUP BY p.id ORDER BY p.created LIMIT 30 </code></pre> doesn't run fast enough, you could always try this: <pre><code>CREATE TEMPORARY TABLE products30 SELECT p.* FROM products p JOIN product_tags_for_products pt4p ON (pt4p.product_id = p.id) JOIN product_tags pt ON (pt.id = pt4p.product_tag_id) WHERE pt.name IN ('some', 'tags', 'here') GROUP BY p.id ORDER BY p.created LIMIT 30 SELECT p.*, GROUP_CONCAT(pt.name) AS tags FROM products30 p LEFT JOIN product_tags_for_products pt4p ON (pt4p.product_id = p.id) LEFT JOIN product_tags pt ON (pt.id = pt4p.product_tag_id) GROUP BY p.id ORDER BY p.created </code></pre> (I used a temp table because you said "no subqueries"; I don't know if they're any easier to use in an Active Record framework, but at least it's another way to do it.) <hr> Ps. One really off-the-wall idea about your original problem: would it make any difference if you changed the <code>GROUP BY p.id</code> clause to <code>GROUP BY p.created, p.id</code>? Probably not, but I'd at least try it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOptimising MySQL query on JOINed tables with GROUP BY and ORDER BY without using nested queries
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USIlmari Karonen
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. This table or related slice is empty.
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.