Hi,
Easiest way is to change the services table to MyISAM
ALTER TABLE `SERVICES` ENGINE=MyISAM;
In theory innodb is less likely to lose data during a power outage and
you can do funky stuff with MariaDB and clustering if you use Innodb but
in reality you can't really use Riv without MyISAM on at least this table.
Regards,
Wayne
On 13/10/14 00:04, Richard Gorbutt wrote:
I've configured RD to be able to import logs from a third party and it
works well, with the following exception. I cannot get the any clock
to stick in the grid from Thurs 1300 to Sun 2300. They refuse to stick
whether I do them manually or a "Change All". I do get the following
error in the syslog.
Oct 12 18:51:20 studio rdlogmanager: invalid SQL or failed DB
connection[Row size too large (> 8126). Changing some columns to TEXT
or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help.
In current row format, BLOB prefix of 768 bytes is stored inline.
QMYSQL3: Unable to execute query]: update SERVICES set
CLOCK120="import" where NAME="Production"
On researching this, I get loads of suggestions to change
innodb_logf_file_size. Tried as high as 512M, (default was 16M I
think), still no joy. Other suggestions showing changing table types
to Barracuda etc. !!!. Apparently from what I read they got more
strict in later mySQL versions.
OS: Linux 17 64bit MATE
RD: 2.9.3 from the Debian Tryphon Rep
MYSQL: 5.5.38-0ubuntu0.14.04.1
I tried a manual change to CLOCK120 in MYSQL Workbench, and same error.
Any other thoughts?
Thanks, Richard
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
