Reply to thread

Message

<blockquote data-quote="MediaPortal-Bot" data-source="post: 869305" data-attributes="member: 48617">Multiple database access can cause the sqlite database to become unavailable when something is written to it. I stumbled upon this problem during the development of aMPdroid/GmaWebservice. For some reason the MP-TvSeries database would sometimes &quot;crash&quot; and after that neither MP-TvSeries nor GmaWebservice could access the sqlite database. A journal file was created (MP-TvSeriesDatabase4.db3.journal) and only after this got deleted the database would become accessible.&lt;br /&gt; &lt;br /&gt; The problem is, that sqlite allows no other locks (not even shared==readonly) when data is written. So when another process has a lock on the database, the client is supposed to wait until the data can be written (which the MediaPortal SQLiteClient doesn't).<a href="http://mantis.team-mediaportal.com/view.php?id=3685" target="_blank">Continue reading...</a></blockquote>

[QUOTE="MediaPortal-Bot, post: 869305, member: 48617"] Multiple database access can cause the sqlite database to become unavailable when something is written to it. I stumbled upon this problem during the development of aMPdroid/GmaWebservice. For some reason the MP-TvSeries database would sometimes "crash" and after that neither MP-TvSeries nor GmaWebservice could access the sqlite database. A journal file was created (MP-TvSeriesDatabase4.db3.journal) and only after this got deleted the database would become accessible. The problem is, that sqlite allows no other locks (not even shared==readonly) when data is written. So when another process has a lock on the database, the client is supposed to wait until the data can be written (which the MediaPortal SQLiteClient doesn't). [url="http://mantis.team-mediaportal.com/view.php?id=3685"]Continue reading...[/url] [/QUOTE]

Verification