StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6823603
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-07-25T23:24:33.330
FavoriteCount
0
LastActivityDate
2011-07-25T23:24:33.330
LastEditDate
2017-05-23T12:26:52.280
LastEditorUserId
-1
OwnerUserId
185988
ParentId
6822026
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Your partitions are fine. Your query's <code>WHERE</code> clause is where the problem lies. When I ran the <code>EXPLAIN PARTITIONS</code> statement on MySQL 5.5, there were two warnings: <pre><code>+---------+------+------------------------------------------------------------------+ | Level | Code | Message | +---------+------+------------------------------------------------------------------+ | Warning | 1292 | Incorrect date value: '2010' for column 'bill_date_bil' at row 1 | | Warning | 1292 | Incorrect date value: '2010' for column 'bill_date_bil' at row 1 | +---------+------+------------------------------------------------------------------+ </code></pre> If you change your query to use a real date like so, it will use the partitions (I didn't include your indexes in my <code>CREATE TABLE</code> statement, which is why they aren't being used): <pre><code>mysql> EXPLAIN PARTITIONS SELECT SQL_NO_CACHE id_bil FROM billing_bil WHERE bill_date_bil < '2010-01-01'; +----+-------------+-------------+------------+--------+---------------+------+---------+------+------+-------+ | id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+-------------+------------+--------+---------------+------+---------+------+------+-------+ | 1 | SIMPLE | billing_bil | p0,p1,p2 | system | NULL | NULL | NULL | NULL | 1 | | +----+-------------+-------------+------------+--------+---------------+------+---------+------+------+-------+ </code></pre> I'm guessing it uses partition <code>p2</code> because MySQL supports partial dates (<code>2010-00-00</code> is less than <code>2010-01-01</code>): <a href="https://stackoverflow.com/questions/2971198/how-to-deal-with-partial-dates-2010-00-00-from-mysql-in-django">How to deal with "partial" dates (2010-00-00) from MySQL in Django?</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmysql partition not working
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USChris Morgan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POmysql partition not working
 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
 VTAcceptedByOriginator
CommentsPostId
1. COwow thanks. I've used the partial date thing for such a long time and the results are always what I expected.... it treated '2011' as 2011-01-01 00:00:00
 singulars
 PostPostId
 PO
 UserUserId
 USbbutle01

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.