home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="doskabouter" data-source="post: 1286642" data-attributes="member: 98267"><p>Ok so if I understand correctly:</p><p>- Writes will be put in the queue and sent to Sqlite asap, and current cache will be updated/invalidated to reflect those changes?</p><p> I can imagine scenarios where the front-end needs something that the write returned (be it an id or something like that) didn't you encounter such cases?</p><ul> <li data-xf-list-type="ul">Reads will be fetched from cache if present, and if not will be read from sqlite (as blocking call), and cache will be updated?</li> <li data-xf-list-type="ul">You will create a new sqlite connection for each and every query? Can't that be a performance-killer?</li> </ul><p></p><p>As for using mpsync: don't know why but it seems to be doing an ok job despite mediaportal locking the database for the whole session...</p><p>Times watched; fine by me.</p><p>Remove dead records: so that only works if you browse inside the directory in mediaportal? So that <em>will</em> keep deleted directories in the database? Not a big problem in my view but might still be a valid usecase for things like mpcleaner then...</p><p>My concern was more that if pc1 has some local files (be it on local c-disk or removable media) those are added in the database and if after that, pc2 starts mediaportal and doesn't have those files present on pc2 it might go deleting those database records.</p><p></p><p>P.S. I might be overthinking all the possible pitfalls of these changes, but that's just how I am <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="doskabouter, post: 1286642, member: 98267"] Ok so if I understand correctly: - Writes will be put in the queue and sent to Sqlite asap, and current cache will be updated/invalidated to reflect those changes? I can imagine scenarios where the front-end needs something that the write returned (be it an id or something like that) didn't you encounter such cases? [LIST] [*]Reads will be fetched from cache if present, and if not will be read from sqlite (as blocking call), and cache will be updated? [*]You will create a new sqlite connection for each and every query? Can't that be a performance-killer? [/LIST] As for using mpsync: don't know why but it seems to be doing an ok job despite mediaportal locking the database for the whole session... Times watched; fine by me. Remove dead records: so that only works if you browse inside the directory in mediaportal? So that [I]will[/I] keep deleted directories in the database? Not a big problem in my view but might still be a valid usecase for things like mpcleaner then... My concern was more that if pc1 has some local files (be it on local c-disk or removable media) those are added in the database and if after that, pc2 starts mediaportal and doesn't have those files present on pc2 it might go deleting those database records. P.S. I might be overthinking all the possible pitfalls of these changes, but that's just how I am :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
Top
Bottom