MySQL Forums :: Partitioning :: Do I have to re write querries when Partitioning?
Re: Do I have to re write querries when Partitioning?
Posted by: Rick James ()
Date: September 03, 2010 07:26PM
PRIMARY KEY (`id`), -- Yes, id is your PK
KEY `part_of_keywords` (`keywords`(30)), -- here's on INDEX
KEY `part_of_category` (`category`), -- here's another
KEY `part_of_country` (`country`(10)),
KEY `part_of_zip` (`zip`),
"INDEX" == "KEY"
PARTITION would make it fast to dump old records. You can probably do that with an ALTER PARTITION instead of DELETE.
To establish partitioning on the table, you would have to make some kind of clumsy change to the PRIMARY KEY.
No changes to INSERT, SELECT, etc are needed.
Any SELECT that does not reference what you are partitioning on will have to search every partition. This means that it is no faster, possibly slower, than if you had a single table.
What do your SELECTs look like?
SHOW TABLE STATUS LIKE 'yspnash_auctions' \G
KEY `part_of_keywords` (`keywords`(30)), -- here's on INDEX
KEY `part_of_category` (`category`), -- here's another
KEY `part_of_country` (`country`(10)),
KEY `part_of_zip` (`zip`),
"INDEX" == "KEY"
PARTITION would make it fast to dump old records. You can probably do that with an ALTER PARTITION instead of DELETE.
To establish partitioning on the table, you would have to make some kind of clumsy change to the PRIMARY KEY.
No changes to INSERT, SELECT, etc are needed.
Any SELECT that does not reference what you are partitioning on will have to search every partition. This means that it is no faster, possibly slower, than if you had a single table.
What do your SELECTs look like?
SHOW TABLE STATUS LIKE 'yspnash_auctions' \G
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.
© 2013, Oracle Corporation and/or its affiliates