Reply to thread

Message

I have posted a new version (1.29.013) to the first post in this thread.

This update contains the following changes:
1) A few bug-fixes;
2) Database rationalization.

The database changes are as follows:
1) 'movieinfo' held date fields - lastupdate, dateadded and datewatched. This means that we only hold this information for movies when they should be held for all videos. I have moved dateadded and lastupdate to the 'movie' table and datewatched to the resume table. It seemed to me that datewatched should always have been stored only when movies have been watched and resume seems like the logical place to do that.
2) 'movie' held information about the watched status. Again, it seems more logical to store watched percent and times watched in the resume table because that data is only relevant when a movie has been watched (which is what the 'resume' table reflects.
3) 'movie' also contained a watched column - indicating whether a movie has been watched. However, the simple presence of a 'resume' entry for a movie tells us that a movie has been watched. The code now checks whether a resume record exists for a movie with a 'stoptime' greater than zero to return whether a movie has been watched.

These are the last changes I propose to make to the database and I feel these changes are worth the extra effort involved.

I recommend that anyone testing the refactored application start again from scratch. However, if you wish to keep your current data, I have provided a script file ('MediaPortalRefactor1.29.013 database changes.sql') containing instructions as to how to manually implement these changes (though I think it would be safer to recreate the Video database from scratch).

Tony

<blockquote data-quote="Anthony Vaughan" data-source="post: 1288392" data-attributes="member: 153283">I have posted a new version (1.29.013) to the first post in this thread.This update contains the following changes:1) A few bug-fixes;2)&nbsp; Database rationalization.The database changes are as follows:&nbsp;1) 'movieinfo' held date fields - lastupdate, dateadded and datewatched. This means that we only hold this information for movies when they should be held for all videos. I have moved dateadded and lastupdate to the 'movie' table and datewatched to the resume table. It seemed to me that datewatched should always have been stored only when movies have been watched and resume seems like the logical place to do that.2) 'movie' held information about the watched status. Again, it seems more logical to store watched percent and times watched in the resume table because that data is only relevant when a movie has been watched (which is what the 'resume' table reflects.3) 'movie' also contained a watched column - indicating whether a movie has been watched. However, the simple presence of a 'resume' entry for a movie tells us that a movie has been watched. The code now checks whether a resume record exists for a movie with a 'stoptime' greater than zero to return whether a movie has been watched.These are the last changes I propose to make to the database and I feel these changes are worth the extra effort involved.I recommend that anyone testing the refactored application start again from scratch. However, if you wish to keep your current data, I have provided a script file ('MediaPortalRefactor1.29.013 database changes.sql') containing instructions as to how to manually implement these changes (though I think it would be safer to recreate the Video database from scratch).Tony</blockquote>

[QUOTE="Anthony Vaughan, post: 1288392, member: 153283"] I have posted a new version (1.29.013) to the first post in this thread. This update contains the following changes: 1) A few bug-fixes; 2) Database rationalization. The database changes are as follows: 1) 'movieinfo' held date fields - lastupdate, dateadded and datewatched. This means that we only hold this information for movies when they should be held for all videos. I have moved dateadded and lastupdate to the 'movie' table and datewatched to the resume table. It seemed to me that datewatched should always have been stored only when movies have been watched and resume seems like the logical place to do that. 2) 'movie' held information about the watched status. Again, it seems more logical to store watched percent and times watched in the resume table because that data is only relevant when a movie has been watched (which is what the 'resume' table reflects. 3) 'movie' also contained a watched column - indicating whether a movie has been watched. However, the simple presence of a 'resume' entry for a movie tells us that a movie has been watched. The code now checks whether a resume record exists for a movie with a 'stoptime' greater than zero to return whether a movie has been watched. These are the last changes I propose to make to the database and I feel these changes are worth the extra effort involved. I recommend that anyone testing the refactored application start again from scratch. However, if you wish to keep your current data, I have provided a script file ('MediaPortalRefactor1.29.013 database changes.sql') containing instructions as to how to manually implement these changes (though I think it would be safer to recreate the Video database from scratch). Tony [/QUOTE]