Database: Refactor MP1 database for multi seat usage (4 Viewers)

[TLD]

I have around 1700 movies and it takes around 10 to 15 minutes to rebuild videos BD. all people need to do is to use .nfo files so you don't lose all the movie info when re scanning there movies.

 

[Anthony Vaughan]

Try TI_MDB

Using that as well .

 

[Anthony Vaughan]

I have around 1700 movies and it takes around 10 to 15 minutes to rebuild videos BD. all people need to do is to use .nfo files so you don't lose all the movie info when re scanning there movies.

I haven't used nfo. When I tried that option it didn't work - for me anyway.

 

[Anthony Vaughan]

I'm looking at actorinfomovie. All of the data it holds is provided elsewhere, more efficiently. When I tried writing to it, all of the fields, except for idActor and role are the same for a given movie. In other words, actorlinkmovie performs that role

In version 1.29, I can't find it being used anywhere. Does anyone know whether this table is used by any extensions?

I can't see why it is there.

 

[Anthony Vaughan]

Actually, I have the same question about IMDBMovies?

 

[Anthony Vaughan]

I think I've worked it out. IMDBMovies and actorinfomovie seem to be used like temporary tables to provide data for the pages below:

I've changed the code (the screens above use the new code) so that this data is got from the movieinfo and actorinfo tables.

As far as I can tell, IMDBMovies and actorinfomovie are now redundant.

 

[ajs]

As far as I can tell, IMDBMovies and actorinfomovie are now redundant.

I didn't understand why, the first table links many films with one actor to get information about him. The second table gives a list of films in which the actor participated, regardless of whether they are in our database or not. And this and that is used and relevant.

 

[Anthony Vaughan]

I didn't understand why, the first table links many films with one actor to get information about him. The second table gives a list of films in which the actor participated, regardless of whether they are in our database or not. And this and that is used and relevant.

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 .

 

[Anthony Vaughan]

Further, to my last comment, the only information I can see about the movies that actors have been in is as follows:

By selecting the title users can see full details about the movie online. Do we need to store anything other than year and role, and the link of course, in our database?

 

[ajs]

Movie - IMDB Info - Actors - Actor - Movies list