Re: Partitioning Table - GPS Data
Posted by:
Rick James
Date: December 01, 2011 09:57PM
PARTITION "pruning" is not possible with a range. You could switch to range partitioning. You would probably have to add a column with the month because partitioning is picky about what it will do ranges over. Or you could use TO_DAYS() in the partition expression.
> `ID` int(64) NOT NULL AUTO_INCREMENT,
That does not give you a 64-bit INT. It gives you a signed 32-bit INT. See BIGINT. Consider UNSIGNED.
> `DDL_LAT` double NOT NULL DEFAULT '0',
> `DDL_LNG` double NOT NULL DEFAULT '0',
Probably overkill.
FLOAT gives you precision better than 6 ft. / 2 meters. DOUBLE gives precision of a few nanometers.
What does your other SELECTs look like?
Subject
Views
Written By
Posted
3684
November 30, 2011 01:53PM
1771
November 30, 2011 03:15PM
Re: Partitioning Table - GPS Data
2069
December 01, 2011 09:57PM
1708
December 02, 2011 08:51AM
1835
December 03, 2011 10:26AM
1780
December 05, 2011 05:43AM
2014
December 06, 2011 08:46PM
1686
December 02, 2011 08:52AM
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.