MySQL Forums :: Partitioning :: No other way than delete primary key to create partitions by single datetime columns?


Advanced Search

Re: No other way than delete primary key to create partitions by single datetime columns?
Posted by: Rick James ()
Date: August 22, 2015 03:35PM

Did you consider adding this, instead of PARTITIONing?

INDEX(createDate)

What query is 'slow'? Maybe some other index would be even better. For example, if you have

WHERE col3 = 123 AND createDate BETWEEN ... AND ...

then this would be optimal (and _better_ than partitioning):

INDEX(col3, createDate)

I'm not saying that PARTITION is _useless_; I am saying that you have not presented a case where it is _more useful_ than some index.

Options: ReplyQuote


Subject Views Written By Posted
No other way than delete primary key to create partitions by single datetime columns? 1281 Sam Young 08/20/2015 08:00PM
Re: No other way than delete primary key to create partitions by single datetime columns? 795 Jonathan Stephens 08/21/2015 02:53AM
Re: No other way than delete primary key to create partitions by single datetime columns? 705 Sam Young 08/23/2015 08:57PM
Re: No other way than delete primary key to create partitions by single datetime columns? 691 Rick James 08/22/2015 03:35PM
Re: No other way than delete primary key to create partitions by single datetime columns? 647 Sam Young 08/23/2015 09:23PM
Re: No other way than delete primary key to create partitions by single datetime columns? 618 Rick James 08/24/2015 12:36PM
Re: No other way than delete primary key to create partitions by single datetime columns? 690 Sam Young 08/26/2015 12:53AM
Re: No other way than delete primary key to create partitions by single datetime columns? 688 Rick James 08/26/2015 10:02AM
Re: No other way than delete primary key to create partitions by single datetime columns? 646 Sam Young 08/26/2015 07:42PM


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.