StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12426789
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-14T14:43:18.320
FavoriteCount
0
LastActivityDate
2012-09-14T15:01:29.897
LastEditDate
2012-09-14T15:01:29.897
LastEditorUserId
980655
OwnerUserId
980655
ParentId
12425831
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
After further investigation, I have discovered several problems with this approach. <ol> <li>It is impossible to range partition on a DATETIME value (which dtime in the example is). <a href="http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-functions.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-functions.html</a></li> <li>The table I was partitioning had a primary key on an auto increment id column, and you cannot partition on an index if there is a different primary key. ERROR 1503 (HY000): A PRIMARY KEY must include all columns in the table's partitioning function See also <a href="http://blog.mclaughlinsoftware.com/2011/05/09/mysqls-real-partition-key/" rel="nofollow">http://blog.mclaughlinsoftware.com/2011/05/09/mysqls-real-partition-key/</a> <a href="http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-partitioning-keys-unique-keys.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-partitioning-keys-unique-keys.html</a></li> <li>WEEK() is not allowed as a partitioning function. <a href="http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-functions.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/partitioning-limitations-functions.html</a></li> </ol> From what I now know, if you have a UNIQUE AUTO_INCREMENT id as the primary key, it is impossible to partition on anything except that value. My queries all use the dtime column in the WHERE conditions, so it seems that unless I can partition somehow on dtime still, there is no benefit to partitioning this table (from a performance perspective). 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMySQL ALTER TABLE with subpartition fails
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJason Martens
UserOwnerUserId
1. USJason Martens
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.