At the current rate, with 1 live user, the JourneyTrackPoints table will contain 50,000 records by (very) early 2014.
With multiple users live, the table is likely to grow in size quite substantially (a six hour drive is likely to create ~4320 records)
Would be wise to split the table before proceeding with any further modifications to the Journeys submodule.
Current thinking is to base the split on the trackID;
The method of calculation could be as simple as
50 is an arbitrary number picked as an example, but a set figure should be chosen as it won't be possible to change it at a later date.
Would be wise to add the calculation to the helper.
As the current Track ID has reached 2704 (due to a resolved bug discovered in VEH-46
) will need to perform a manual split of the existing data in the live database.
The cron run should check whether the limit is being approached and create a new table if it's near.
Would also be wise to store the current table number somewhere so that various routines (especially cron) can quickly look it up