Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1077396" data-attributes="member: 18896">Database corruption can sneak in when you least expect it. Shutting down MediaPortal and then re-opening it, sometimes leads to the previous session not fully closed yet. This leads to simultainious access to the databases if plugins are still updating things on a background thread, which SQLite does not enjoy unless this is all coded in safely for concurrent access. Another reason can be an unexpected shutdown before the database was properly saved, or dozens of other reasons. It is actually amazing how rare corruption occurs. Moving-Pictures runs many self-repair routines when it initializes, which is more self-evident when you launch the configuration panel.&nbsp;Not saying that is what happened to you, but it would not be the first time. You would be wise to run a backup script, such as the one I use myself that I shared on the forum (simple batch script). It is an auto-backup/restore script that works by checking the integrity of the SQLite database. That way if a corruption is detected it immediatly restores the last known-good backup.&nbsp;As for all your manual approvals, you could have given IMDb+ a try as it has an improved auto-matching rate and offers additional benefits that you might enjoy. Another suggestion is to use a 3rd party tool such as MovPicNFO or the Moving-Pictures build in file-renamer, so that the IMDb tt-ID is secured in either NFO file or filename (MovPicNFO can also store other data inside the NFO as well as artwork for a full off-line re-import via XBMC scraper).</blockquote>

[QUOTE="RoChess, post: 1077396, member: 18896"] Database corruption can sneak in when you least expect it. Shutting down MediaPortal and then re-opening it, sometimes leads to the previous session not fully closed yet. This leads to simultainious access to the databases if plugins are still updating things on a background thread, which SQLite does not enjoy unless this is all coded in safely for concurrent access. Another reason can be an unexpected shutdown before the database was properly saved, or dozens of other reasons. It is actually amazing how rare corruption occurs. Moving-Pictures runs many self-repair routines when it initializes, which is more self-evident when you launch the configuration panel. Not saying that is what happened to you, but it would not be the first time. You would be wise to run a backup script, such as the one I use myself that I shared on the forum (simple batch script). It is an auto-backup/restore script that works by checking the integrity of the SQLite database. That way if a corruption is detected it immediatly restores the last known-good backup. As for all your manual approvals, you could have given IMDb+ a try as it has an improved auto-matching rate and offers additional benefits that you might enjoy. Another suggestion is to use a 3rd party tool such as MovPicNFO or the Moving-Pictures build in file-renamer, so that the IMDb tt-ID is secured in either NFO file or filename (MovPicNFO can also store other data inside the NFO as well as artwork for a full off-line re-import via XBMC scraper). [/QUOTE]

Verification