On Dec 5, 2013, at 11:25 58, Wayne Merricks <[email protected]> wrote:
> Potentially to "fix" this you have a few approaches: > > * Set the initial SQL create statements to include a MyISAM table create > statement for the SERVICES table > * Refactor the SERVICES table so that there isn't 248 columns per record. Which would also break SQL portability (which I guess is not really an issue, as I am aware of no one running RD with an alternative RDBMS). > Refactoring is probably the way to go but its not a small amount of work. > Off the top of my head you could separate off all 168 clock fields into their > own table, something like: > > CLOCK_NAME: Name of the clock, same as CLOCK1 - 168 at the moment > SLOT: value 1 - 168 to replace the CLOCK1 - 168 columns > SERVICE: Name of the service this clock belongs to An arguably better design in terms of data normalization. As you observe though, it wouldn’t be a trivial amount of work. :) Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | All science is either physics or stamp collecting. | | -- Ernest Rutherford | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
