Bug #29120 | new partition type | ||
---|---|---|---|
Submitted: | 14 Jun 2007 18:31 | Modified: | 5 Apr 2011 6:03 |
Reporter: | Roberto Spadim (Basic Quality Contributor) | Email Updates: | |
Status: | Open | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S4 (Feature request) |
Version: | any | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | qc |
[14 Jun 2007 18:31]
Roberto Spadim
[15 Jun 2007 7:22]
Valeriy Kravchuk
Thank you for a reasonable feature request.
[18 Aug 2009 22:01]
Mattias Jonsson
I don't see how this will ensure the uniqueness of the primary key / unique key, and if a row can go to partition 1 OR 2 how could that be deterministic? Could you please give a more detailed explanation over how this new type of partitioning should work?
[18 Sep 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[29 Mar 2011 18:56]
Roberto Spadim
hi guys, i was reading again: it´s not deterministic i see it now it´s a problem since we must read from partition 1 and 2 (not a optimized feature) the nice part is OTHERS VALUES could it be implemented? i don´t know if it´s a duplicated of others bugs since this one is very old (2007)
[5 Apr 2011 6:03]
Roberto Spadim
in this case unique/primary keys must be at table level (not at partition level) rows and others indexes could/should be at partitions