| Bug #40372 | Dynamic partitoned Tables | ||
|---|---|---|---|
| Submitted: | 28 Oct 2008 14:13 | Modified: | 12 Jan 2009 11:32 |
| Reporter: | Frank Mussmann | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S4 (Feature request) |
| Version: | somewhere in future | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Partitioned Tables | ||
[12 Jan 2009 11:32]
Mattias Jonsson
Duplicate of bug#30346. Also see: http://datacharmer.blogspot.com/2008/12/partition-helper-improving-usability.html

Description: When creating a table like this: CREATE TABLE trb3 (id INT, name VARCHAR(50), purchased DATE) PARTITION BY RANGE( YEAR(purchased) ) ( PARTITION p0 VALUES LESS THAN (1990), PARTITION p1 VALUES LESS THAN (1995), PARTITION p2 VALUES LESS THAN (2000), PARTITION p3 VALUES LESS THAN (2005) ); I think it would be great by creating a table which is dynamic. Just thinking about dropping Partitions for deleting would be perfect. My suggestion would be: CREATE TABLE trb3 (id INT, name VARCHAR(50), purchased DATE) PARTITION BY RANGE( YEAR(purchased) ) ); This should create one Partition for EACH YEAR - completely in the background and dynamically. I don't want to think about creating new partitions while running a database and forgetting about things or creating CRONs or Sheduled Tasks. Just a dynamic Partition would fix it. How to repeat: ----- Suggested fix: -----