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
MediaPortal 1 Talk
xmltv - guide to channel mapping
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="dvdfreak" data-source="post: 161138" data-attributes="member: 21313"><p>What you describe will of course also work, but that's not what I was suggesting actually.</p><p></p><p>What I suggest we have is:</p><p></p><p>TvProgram -- (many-2-one) --> TvChannel -- (one-2-many) --> TuningChannel</p><p></p><p>This would be a very clean way to keep guide information in its own little subdomain. While usually a TuningChannel will have a one-2-one relationship with a TvChannel, it will actually be possible to have two TuningChannels use the same TvChannel, so the same guide data.</p></blockquote><p></p>
[QUOTE="dvdfreak, post: 161138, member: 21313"] What you describe will of course also work, but that's not what I was suggesting actually. What I suggest we have is: TvProgram -- (many-2-one) --> TvChannel -- (one-2-many) --> TuningChannel This would be a very clean way to keep guide information in its own little subdomain. While usually a TuningChannel will have a one-2-one relationship with a TvChannel, it will actually be possible to have two TuningChannels use the same TvChannel, so the same guide data. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
xmltv - guide to channel mapping
Contact us
RSS
Top
Bottom