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="Anthony Vaughan" data-source="post: 1287163" data-attributes="member: 153283"><p>Thank you for letting me know about this. When I modified the code to handle stacked movies properly, I forgot to change the upgrade code <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /> .</p><p></p><p>I would expect, when the database is not loaded correctly, for the rest of the app to become unstable - so a crash wold be expected. This got me thinking about what to do when an upgrade fails. Maybe the answer, so users can keep using the system, is to load the default version of the database when something goes wrong so users can at least do something; maybe putting a log entry in to say that the upgrade process failed and to contact MP.</p><p></p><p>Of course, this shouldn't happen once I've fixed the bug.</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1287163, member: 153283"] Thank you for letting me know about this. When I modified the code to handle stacked movies properly, I forgot to change the upgrade code :( . I would expect, when the database is not loaded correctly, for the rest of the app to become unstable - so a crash wold be expected. This got me thinking about what to do when an upgrade fails. Maybe the answer, so users can keep using the system, is to load the default version of the database when something goes wrong so users can at least do something; maybe putting a log entry in to say that the upgrade process failed and to contact MP. Of course, this shouldn't happen once I've fixed the bug. [/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