Reply to thread

Message

I thought I should let you know exactly what changes I have made to VideoDatabase5.db3. They are as follows:
Move strFilename from files to movie;
Remove files table;
Remove duration;
Remove hasSubtitles from filesmediainfo.
Both duration and hasSubtitles were being stored in two places and I have rationalized that.

I have amended all processing related to these changes throughout the application.

These changes mean that duration, watched, times watched and watched percent are all available straight from movie (which is used to identify a video throughout, anyway). So there is no need to handle duration separately from the core processing (which it needs to do currently).

Getting rid of the files table, which was superfluous, and removing the duplication of hasSubtitles and duration, has simplified processing considerably.

I hope this helps you to understand why I felt it was necessary to change the database layout before handling the multi-user issue. I think it'll really be worth it in the end.

Tony

<blockquote data-quote="Anthony Vaughan" data-source="post: 1286235" data-attributes="member: 153283">I thought I should let you know exactly what changes I have made to VideoDatabase5.db3. They are as follows:<ol>
<li data-xf-list-type="ol">Move strFilename from files to movie;</li>
<li data-xf-list-type="ol">Remove files table;</li>
<li data-xf-list-type="ol">Remove duration;</li>
<li data-xf-list-type="ol">Remove hasSubtitles from filesmediainfo.</li>
</ol>Both duration and hasSubtitles were being stored in two places and I have rationalized that. I have amended all processing related to these changes throughout the application.These changes mean that duration, watched, times watched and watched percent are all available straight from movie (which is used to identify a video throughout, anyway). So there is no need to handle duration separately from the core processing (which it needs to do currently).Getting rid of the files table, which was superfluous, and removing the duplication of hasSubtitles and duration, has simplified processing considerably.I hope this helps you to understand why I felt it was necessary to change the database layout before handling the multi-user issue. I think it'll really be worth it in the end.Tony</blockquote>

[QUOTE="Anthony Vaughan, post: 1286235, member: 153283"] I thought I should let you know exactly what changes I have made to VideoDatabase5.db3. They are as follows: [LIST=1] [*]Move strFilename from files to movie; [*]Remove files table; [*]Remove duration; [*]Remove hasSubtitles from filesmediainfo. [/LIST] Both duration and hasSubtitles were being stored in two places and I have rationalized that. I have amended all processing related to these changes throughout the application. These changes mean that duration, watched, times watched and watched percent are all available straight from movie (which is used to identify a video throughout, anyway). So there is no need to handle duration separately from the core processing (which it needs to do currently). Getting rid of the files table, which was superfluous, and removing the duplication of hasSubtitles and duration, has simplified processing considerably. I hope this helps you to understand why I felt it was necessary to change the database layout before handling the multi-user issue. I think it'll really be worth it in the end. Tony [/QUOTE]