Reply to thread

Message

<blockquote data-quote="MediaPortal-Bot" data-source="post: 779371" data-attributes="member: 48617">The current SQLite implementation of MediaPortal has many flaws, especially with multiple access/dbs on network shares. One of the reasons is that we're using SqLite 3.6.6.1 from 2008. There have been a number of releases since then with lots of improvements/bugfixes (Release History Of SQLite).The SQLite implementation should be reworked in one of the following ways:a) update our wrapper to use the latest sqlite version orb) instead use an external .NET wrapper (e.g. System.Data.SQLite: About ). We could keep our class (SQLiteClient) to be backward compatible, but instead of using our own wrapper code just call the appropriate .NET functions of the library.<a href="http://mantis.team-mediaportal.com/view.php?id=3687" target="_blank">http://mantis.team-mediaportal.com/view.php?id=3687</a><a href="http://mantis.team-mediaportal.com/view.php?id=3687" target="_blank">Open the issue in Mantis...</a></blockquote>

[QUOTE="MediaPortal-Bot, post: 779371, member: 48617"] The current SQLite implementation of MediaPortal has many flaws, especially with multiple access/dbs on network shares. One of the reasons is that we're using SqLite 3.6.6.1 from 2008. There have been a number of releases since then with lots of improvements/bugfixes (Release History Of SQLite). The SQLite implementation should be reworked in one of the following ways: a) update our wrapper to use the latest sqlite version or b) instead use an external .NET wrapper (e.g. System.Data.SQLite: About ). We could keep our class (SQLiteClient) to be backward compatible, but instead of using our own wrapper code just call the appropriate .NET functions of the library. [url]http://mantis.team-mediaportal.com/view.php?id=3687[/url] [url=http://mantis.team-mediaportal.com/view.php?id=3687]Open the issue in Mantis...[/url] [/QUOTE]

Verification