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: 1286835" data-attributes="member: 153283"><p>Okay. So, if I understand you correctly, you are saying that we hold information about a separate set of movies from the ones users have, that actors have worked in, and that we are holding that data purely for information purposes (to furnish the actor screens in the configuration application). That makes sense to me. What doesn't make sense to me is the way the data is being stored because actorinfomovies repeats a great deal of the information in IMDBMovies. I think I can rationalize the data to make it work much more efficiently.</p><p></p><p>I have searched the entire MP application and the only places these tables are used are as follows:</p><p></p><p>actorinfomovie - VideoDatabaseSqlLite.cs </p><p>IMDBMovie - GUIVideoArtistInfo.cs and VideoDatabaseSqlLite.cs</p><p></p><p>So, it won't take me much effort to refactor this code to make it work better and, hopefully, make its purpose more obvious <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="Anthony Vaughan, post: 1286835, member: 153283"] Okay. So, if I understand you correctly, you are saying that we hold information about a separate set of movies from the ones users have, that actors have worked in, and that we are holding that data purely for information purposes (to furnish the actor screens in the configuration application). That makes sense to me. What doesn't make sense to me is the way the data is being stored because actorinfomovies repeats a great deal of the information in IMDBMovies. I think I can rationalize the data to make it work much more efficiently. I have searched the entire MP application and the only places these tables are used are as follows: actorinfomovie - VideoDatabaseSqlLite.cs IMDBMovie - GUIVideoArtistInfo.cs and VideoDatabaseSqlLite.cs So, it won't take me much effort to refactor this code to make it work better and, hopefully, make its purpose more obvious :) . [/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