The Problem has to due with the length of data for the clocks table, One way would be to update the SERVICES Table so that CLOCK0 to CLOCK176 are char(3)
This should work because I believe that the the clock code is limited to three (3) characters. T.J. 2011/11/20 Sébastien Leblanc <[email protected]> > On Sun, Nov 20, 2011 at 16:15, Pierre-Luc Gauthier > <[email protected]> wrote: > > Hi there, > > > > I do want to thank everybody on this mailing list for your help and > support > > and especially Fred Gleason for his wonderful software. > > > > Last week I've successfully compiled Rivendell 2.1.1 on Arch Linux. > > Fooled around with it and started a new database from scratch. So no > > database updating here, it's a bran new one. > > > > So I went into creating simple events and simple clocks and peppered them > > into my grid leaving empty slots in the grid. > > Generated some logs with rdlogmanager and got them running for a few > days in > > rdairplay. > > So far so good. > > > > But, today I created many more clocks. Still everything is fine here. The > > problem starts when trying to add any clocks to an empty grid. > > RdLogManager -> Edit Grids -> "MyGrid" -> Edit -> "Clicked on any empty > > clock" -> "Selected whatever clock" -> OK > > The Clock is added in the "Grid edition" interface BUT is not added in > > mysql. The CLOCKx row in the SERVICE table still displays a NULL value. > > Moreover, if I close and reopen the "Grid edition" interface, the newly > > added clock has disappeared. > > > > So I started trouble shooting the situation with RdLogManager: > > I can change the clock in an already attributed slot in the grid. > > But I cannot change the clock in an empty slot in the grid. > > > > With mysql-workbench: > > I can manually change the clock in an already attributed slot in the > grid. > > But I cannot change the clock in an empty slot in the grid. > > And if I try to do so, I get this message: > > ERROR 1118: Row size too large. The maximum row size for the used table > > type, not counting BLOBs, is 8126. You have to change some columns to > TEXT > > or BLOBs > > SQL Statement: > > UPDATE `Rivendell`.`SERVICES` SET `CLOCK7`='102' WHERE `NAME`='clg2' > > > > So that's where I am so far. > > Any hints on what could resolve the issue? > > > > Thank you so very much. > > > > -- > > Pierre-Luc Gauthier > > We apparently fixed it by changing the storage engine for SERVICES > from InnoDB to MyISAM. Since Rivendell does not use advanced features > of InnoDB (e.g. foreign keys) I do not think there will be an issue > with this. > > -- > Sébastien Leblanc > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
