Reply to thread

Message

<blockquote data-quote="megahorst" data-source="post: 966196" data-attributes="member: 22213">I had a deeper look to the database.&nbsp;All the tables where stored as MyISAM tables.&nbsp;I have converted them with the SQL-workbench.[code]alter table `mptvdb`.`&lt;tablename&gt;` engine=innodb;[/code]&nbsp;That worked at most tables.But&nbsp; recording and schedulegave me the following error:[code]0&nbsp; &nbsp; 2&nbsp; &nbsp; 19:48:42&nbsp; &nbsp; alter table `mptvdb`.`recording` engine=innodb&nbsp; &nbsp; Error Code: 1071. Specified key was too long; max key length is 767 bytes&nbsp; &nbsp; 0.031 sec[/code]&nbsp;All the others gave my the following warning:[code]1&nbsp; &nbsp; 4&nbsp; &nbsp; 19:58:37&nbsp; &nbsp; alter table `mptvdb`.`card` engine=innodb&nbsp; &nbsp; 3 row(s) affected, 2 warning(s):1478 InnoDB: ROW_FORMAT=DYNAMIC requires innodb_file_format &gt; Antelope.1478 InnoDB: assuming ROW_FORMAT=COMPACT.Records: 3&nbsp; Duplicates: 0&nbsp; Warnings: 2&nbsp; &nbsp; 0.109 sec[/code]&nbsp;Does anybody have an idea what has to modified within the db?</blockquote>

[QUOTE="megahorst, post: 966196, member: 22213"] I had a deeper look to the database. All the tables where stored as MyISAM tables. I have converted them with the SQL-workbench. [code]alter table `mptvdb`.`<tablename>` engine=innodb;[/code] That worked at most tables.But recording and schedule gave me the following error: [code]0 2 19:48:42 alter table `mptvdb`.`recording` engine=innodb Error Code: 1071. Specified key was too long; max key length is 767 bytes 0.031 sec[/code] All the others gave my the following warning: [code]1 4 19:58:37 alter table `mptvdb`.`card` engine=innodb 3 row(s) affected, 2 warning(s): 1478 InnoDB: ROW_FORMAT=DYNAMIC requires innodb_file_format > Antelope. 1478 InnoDB: assuming ROW_FORMAT=COMPACT. Records: 3 Duplicates: 0 Warnings: 2 0.109 sec[/code] Does anybody have an idea what has to modified within the db? [/QUOTE]

Verification