Reply to thread

Message

<blockquote data-quote="arion_p" data-source="post: 865609" data-attributes="member: 45945">This has nothing to do with the way EPG is imported. EPG is stored in the database. If the database is corrupt, you cannot import EPG no matter what method you use.The problem is that by default MySQL uses MyISAM engine which is not transactional. If a power failure or other unexpected system shutdown occurs, data may not have been flushed from memory to disk and the database gets corrupt. There is another engine, InnoDB, which is transactional and does not suffer from this issue (unless the filesystem itself gets corrupt), but it comes at a cost: speed. InnoDB is considerably slower than MyISAM. If you expect your system to be randomly powered off without proper shutdown you may want to convert your database to InnoDB.&nbsp;Another option is to use MSSQL (Express) which is always transactional and also does not suffer from this issue. It is also slower than MyISAM but to my experience faster than InnoDB (no&nbsp; have not performed any benchmarks so I may be wrong). But MSSQL by default uses ANSI encoding for strings which means only characters from a single ANSI charset are supported. If you need characters from non-latin character sets (such as Greek, Cyrillic, etc) you need either MySQL or you need to change the database fields from varchar to nvarchar. Unless you know what you are doing I suggest you avoid it.</blockquote>

[QUOTE="arion_p, post: 865609, member: 45945"] This has nothing to do with the way EPG is imported. EPG is stored in the database. If the database is corrupt, you cannot import EPG no matter what method you use. The problem is that by default MySQL uses MyISAM engine which is not transactional. If a power failure or other unexpected system shutdown occurs, data may not have been flushed from memory to disk and the database gets corrupt. There is another engine, InnoDB, which is transactional and does not suffer from this issue (unless the filesystem itself gets corrupt), but it comes at a cost: speed. InnoDB is considerably slower than MyISAM. If you expect your system to be randomly powered off without proper shutdown you may want to convert your database to InnoDB. Another option is to use MSSQL (Express) which is always transactional and also does not suffer from this issue. It is also slower than MyISAM but to my experience faster than InnoDB (no have not performed any benchmarks so I may be wrong). But MSSQL by default uses ANSI encoding for strings which means only characters from a single ANSI charset are supported. If you need characters from non-latin character sets (such as Greek, Cyrillic, etc) you need either MySQL or you need to change the database fields from varchar to nvarchar. Unless you know what you are doing I suggest you avoid it. [/QUOTE]

Verification