Not as far as I'm aware or at least nobody else has complained around here about it.
Its not a problem for the Riv appliance as CentOS is a few versions behind on MySQL. As you found out its only really when you start using Wheezy or Ubu 12.04+ as a base that you get problems. 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. Failing that setting the Riv code to explicitly create the tables with MyISAM is probably a good start. Regards, Wayne On 2013-01-26 20:20, Jay Eames wrote: > Thanks Wayne, Absolutely spot on with that info. > > Are there any other tables Im likely to run into issue with? > > On 26 January 2013 20:04, waynemerricks > <[email protected] [3]> wrote: > >> Sounds like the Innodb problem. In the newer versions of MySQL >> innodb >> becomes the standard db engine. This has issues because the row >> byte >> length cant support the full row of grid clocks. Check the SQL >> for the >> SERVICES table and see whether its set to Innodb or not. >> >> If it is dump the table, change the innodb bit to myisam then drop >> and >> reimport the table. >> >> On 2013-01-26 18:42, Jay Eames wrote: >> > Hi guys, >> > >> > II am having a bit of a problem with a fresh install of >> Rivendell, >> > using the latest ubuntu packages. >> > >> > As I was creating a new grid, I got half way through assigning >> > clocks, >> > when I started receiving these messages: >> > >> > invalid SQL or failed DB connection: update SERVICES set >> CLOCK89="" >> > where NAME="Main >> Service" >> > Database connection failed: update SERVICES set CLOCK89="" >> >> > where NAME="Main Service" >> > Database connection restored. >> > >> > I now cannot assign clocks to the grid at all. >> > >> > The clock was successfully used on previous grid slots without >> issue. >> > Nothing was changed between it working and it not. I have >> rebooted >> > etc, but still no luck. >> > >> > Any ideas? >> > >> > Jay >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] [1] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev [2] _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
