On Jan 26, 2013, at 15:29 25, waynemerricks wrote: > Its something to look at for riv as a whole moving forwards as Innodb > is a good driver to use as it has better data integrity. I guess a > really simple solution would be to split the services table into two, I > don't really know if you can increase the Innodb max row length. Thats > a google for another day.
The real solution will be to normalize the schema in that table properly -- i.e. move all the CLOCK<n> fields to their own table with keys to relate them to the parent SERVICES record and the appropriate hours. > Failing that setting the Riv code to explicitly create the tables with > MyISAM is probably a good start. This should arguably be a user-specified option when creating a new database. Cheers! |-------------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-------------------------------------------------------------------------| | Some people say a front-engine car handles best. Some people say a | | rear-engine car handles best. I say a rented car handles best. | | --P.J. O'Rourke | |-------------------------------------------------------------------------| _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
