MySQL Forums
Forum List  »  Partitioning

Re: Auto_increment generated id as the Partioning Key
Posted by: Mikael Ronström
Date: March 21, 2006 04:24PM


Jon Freitag wrote:
> Are there any limitations with respect to tables
> using an auto_increment generated id as the
> partioning key? I am running into some problems
> with MySQL 5.1.7-beta on Linux with partitioned
> tables that seems to be related to the auto
> increment.

The basics should work. If auto increment is combined with
replication we mey get into the gray zone but I know of no
problem with just basic auto increment.

> First of all when I try to drop a partition that I
> am no longer writing data to, while writing data
> to another partition, MySQL seems to delete data
> in all partitions. As new records are written to
> another partition, the auto generated ids are 1,
> 257, 65793, 16843009, 4311810305, 1.10382E+12,
> 2.82579E+14 respectively. The subsequent insert
> fails with a range error for the datatype. Seems
> like the values are being incremented to the
> maximum value for various integer data types.

Sounds like a bug to me. Please file a bug report with some details
of what you do to get the erratic behaviour and we'll quickly look into it.

> Any insight is appreciated.

Rgrds Mikael

> Edited 1 times. Last edit at 03/21/06 05:09PM by
> Edwin DeSouza.

Mikael Ronstrom
Senior Software Architect, MySQL AB
My blog:

Options: ReplyQuote

Written By
Re: Auto_increment generated id as the Partioning Key
March 21, 2006 04:24PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.