Home/ Questions/Q 501113
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T06:09:23+00:00

I have a table that essentially looks like this: CREATE TABLE myTable ( id

  • 0

I have a table that essentially looks like this:

CREATE TABLE myTable (
    id INT auto_increment,
    field1 TINYINT,
    field2 CHAR(2),
    field3 INT,
    theDate DATE,
    otherStuff VARCHAR(20)
    PRIMARY KEY (id)
    UNIQUE KEY (field1, field2, field3)
)

I’d like to partition the table based on the month and year of theDate, however the manual is telling me I’m not allowed:

All columns used in the partitioning expression for a partitioned table must be part of every unique key that the table may have. In other words, every unique key on the table must use every column in the table’s partitioning expression

What are my options here? Can I still partition the table?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I wrote a blog post about this issue here Scaling Rails with MySQL table partitioning (rails uses integer PKs). The same technique should work in your case, except, unfortunately you have to drop the [field1, field2, field3] unique key.

    Dropping a unique key was a problem I dealt with too (though not mentioned in the post). I worked around it by implemented an existence check before creating the record, realizing that we’d still get occasional dupes due to the race condition. In practice, that didn’t turn out to be a problem. However, the increased query throughput required scaling up the innodb buffer size ’cause the i/o’s we’re brutal.

    • 0