waynemerricks
commented
9 years ago This is a common problem. In MySQL < 5.5 the default database engine was MyISAM unless otherwise specified. After 5.5 InnoDB is now the default which introduced the lower row limit.
VARCHAR fixed the problem because MySQL stores varchars, blobs and probably some others outside of the rows themselves. This has a small performance impact on row retrieval but for most people/work loads apart from very high numbers of users you'd never really notice.
I suppose a better fix would be to specify MyISAM but then that may interfere with RD's use on different databases. The longer term fix would probably be a restructure on SERVICES where the days are split into rows e.g.
Date, Clock No, Slot, Service_ID
Then you could do slot 0 - 23 per day (or even a clock 0 - 23 per day so each row was a single day), have the date and clock number look up. At the moment each row is an entire weeks worth of clocks including all the other service info in the SERVICES table.
In theory you could do some table joins to present back to Riv the same format of data it expects from the single row per week scenario. I might have a play with that as code wise it is trivial to swap out a single SQL statement vs a whole bunch of extra lookups and code rewrites.
ElvishArtisan
albanpeignier
dthertel
After a clean install on Ubuntu14.04 experienced problem with not being able to set grids between Thursday 12:00 - end of week.
after look up of issue (http://dev.mysql.com/doc/refman/5.0/en/column-count-limit.html) appears to be a limit of row size capacity in newer MySQL. I changed my local DB from CHAR(60) to VARCAHR(60) for grid# and appears to have resolved the issue.