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
Improvement Suggestions
VideoDatabaseV5 design issue
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: 1285330" data-attributes="member: 153283"><p>The link between movie and files is still there: files is the parent and movie is the child.</p><p></p><p>This is a relational database. In the real world, path is the main table and files is a child of path and movie should be a child of files. The existing structure has a redundant relationship where movie has been placed above files and below path - but there is a link between path and files and path > movie > files. Surely, in the real world, a movie is a type of file as opposed to a video or another type of file.</p><p></p><p>I'll leave it there. Please bear in mind that I am not just making this up as I go along - Kodi uses the structure I am suggesting (so it really is a working solution).</p><p></p><p>For me this is serious enough for me to me looking at other front-ends. The server side is great but I have had numerous problems with the client-side, particularly when adding movies to the database.</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1285330, member: 153283"] The link between movie and files is still there: files is the parent and movie is the child. This is a relational database. In the real world, path is the main table and files is a child of path and movie should be a child of files. The existing structure has a redundant relationship where movie has been placed above files and below path - but there is a link between path and files and path > movie > files. Surely, in the real world, a movie is a type of file as opposed to a video or another type of file. I'll leave it there. Please bear in mind that I am not just making this up as I go along - Kodi uses the structure I am suggesting (so it really is a working solution). For me this is serious enough for me to me looking at other front-ends. The server side is great but I have had numerous problems with the client-side, particularly when adding movies to the database. Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
VideoDatabaseV5 design issue
Contact us
RSS
Top
Bottom