Reply to thread

Message

<blockquote data-quote="Lehmden" data-source="post: 1127968" data-attributes="member: 109222">Hi.We have encounter the same while developing SQLite DB plugin for MP2 server, so no big surprise. If you optimize SQLite for speed the difference even gets bigger (up to a factor of 4 means SQLite is four times as fast as MySQL when used as DB backend for MP2 server). So for MP2 there is an easy choice... But in this use-case you need to think about multiple write access at the same time, something SQLite did not like that much. MP2 server is handling all access to the DB, so no issue there, but in MP1 case you can not prevent simultaneous write access in all circumstances.There also is a difference and this may be the reason why the centralized MySQL DB is no part of the regular Kodi release...Due to the proper .nfo support a centralized DB is not that important for Kodi than it is for MP. Simply hit &quot;save DB&quot; in GUI and all metadata incl. watched status is saved near to the media. Every client now can access this (and normally did this during startup) so a sync is done semi- automatically once per run...</blockquote>

[QUOTE="Lehmden, post: 1127968, member: 109222"] Hi. We have encounter the same while developing SQLite DB plugin for MP2 server, so no big surprise. If you optimize SQLite for speed the difference even gets bigger (up to a factor of 4 means SQLite is four times as fast as MySQL when used as DB backend for MP2 server). So for MP2 there is an easy choice... But in this use-case you need to think about multiple write access at the same time, something SQLite did not like that much. MP2 server is handling all access to the DB, so no issue there, but in MP1 case you can not prevent simultaneous write access in all circumstances. There also is a difference and this may be the reason why the centralized MySQL DB is no part of the regular Kodi release... Due to the proper .nfo support a centralized DB is not that important for Kodi than it is for MP. Simply hit "save DB" in GUI and all metadata incl. watched status is saved near to the media. Every client now can access this (and normally did this during startup) so a sync is done semi- automatically once per run... [/QUOTE]

Verification