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="ajs" data-source="post: 1285331" data-attributes="member: 68833"><p>This simplifies queries, especially in the Database view mode.</p><p></p><p>In the world of Mediaportal the path is secondary, and Movie is primary. We play from the Movie everywhere, and all other tables are attributes.</p><p></p><p>Kodi has its own problems in the structure, but it is as it is, our ideology is a bit different, on the one hand we have the primary Path, but it is primary in the viewer, on the other hand we have the primary Movie, and everything else is secondary attributes, this is true for the viewer mode - database. </p><p></p><p>We can change the structure as you ask, but it is a waste of time which will not improve. Because the mechanism of adding information comes from Movie (if my memory serves me right) but not from path or file...</p><p></p><p>We don't have a server part, only a client part, just like Kodi. I am with Mediaportal since version 0.8 (if memory serves me correctly) and now I have more than 500 movies in the Movie Library, and in all that time there was not a single database corruption or database crash. The database gradually migrates from one version to another, on the test computer sometimes goes through a complete re-import, but on the other 3 НТРС database is stable and works like clockwork.</p></blockquote><p></p>
[QUOTE="ajs, post: 1285331, member: 68833"] This simplifies queries, especially in the Database view mode. In the world of Mediaportal the path is secondary, and Movie is primary. We play from the Movie everywhere, and all other tables are attributes. Kodi has its own problems in the structure, but it is as it is, our ideology is a bit different, on the one hand we have the primary Path, but it is primary in the viewer, on the other hand we have the primary Movie, and everything else is secondary attributes, this is true for the viewer mode - database. We can change the structure as you ask, but it is a waste of time which will not improve. Because the mechanism of adding information comes from Movie (if my memory serves me right) but not from path or file... We don't have a server part, only a client part, just like Kodi. I am with Mediaportal since version 0.8 (if memory serves me correctly) and now I have more than 500 movies in the Movie Library, and in all that time there was not a single database corruption or database crash. The database gradually migrates from one version to another, on the test computer sometimes goes through a complete re-import, but on the other 3 НТРС database is stable and works like clockwork. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
VideoDatabaseV5 design issue
Contact us
RSS
Top
Bottom