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
Support
General Support
MP1-4502 - ChannelState.DoSetChannelStates: An unknown error occured while setting channel states
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="mm1352000" data-source="post: 1062954" data-attributes="member: 82144"><p>I'm absolutely serious. Maybe "harmless" wasn't the best choice of word, but the "not related to the crash" part definitely says what I meant to say. I'm interested in focusing on the crash. I'm not interested in investigating the exception unless it is related to the crash or some other serious problem.</p><p></p><p></p><p>As above: maybe "harmless" wasn't the best choice of word. However these days some developers use exception throwing and catching routinely. In other words, exceptions don't always point to a fatal condition or failure that ought to be exhaustively investigated and fixed.</p><p></p><p></p><p>Sure. If an exception is causing some kind of error or bug - for example, the UI fails to load a channel list or EPG data - then sure it might be necessary to investigate and fix something. However most of the time with MP database related exceptions this is not the case.</p><p></p><p>In this case I have yet to see any evidence that the exception you're referring to is related to the crash. I also don't see any evidence that it is causing any kind of error or bug. If you have evidence then please by all means provide it.</p><p></p><p></p><p>I'm not sure what you want me to do with this information.</p><p>Please understand that I'm working within a much larger context. TVE 3 uses a third party persistence framework (gentle.NET) to handle all the database related stuff. That framework is no longer being developed. Most of my time working on MP these days is spent on TVE 3.5, which has removed gentle.net in favour of Microsoft's Entity Framework. TVE 3.5 is already in use with MP2, and I'm hoping a version for MP1 will be released this year.</p><p></p><p>In my opinion it is not worth my time investigating such database exceptions with TVE 3 unless they are really causing operational or reliability problems. gentle.net is going away and my belief is that these sorts of exceptions will go away with it. EF will bring its own set of challenges.</p><p></p><p>Does this help you understand my perspective? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>Nope, I can't explain it.</p><p>As above: TV Server doesn't interact with the database directly. Everything goes through the gentle.NET framework which I consider obsolete. Gentle.NET is responsible for converting code expressions to queries which are database engine specific. It is entirely possible that some of these queries are not as efficient as they could be. That is a common tradeoff when using a database abstraction layer.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1062954, member: 82144"] I'm absolutely serious. Maybe "harmless" wasn't the best choice of word, but the "not related to the crash" part definitely says what I meant to say. I'm interested in focusing on the crash. I'm not interested in investigating the exception unless it is related to the crash or some other serious problem. As above: maybe "harmless" wasn't the best choice of word. However these days some developers use exception throwing and catching routinely. In other words, exceptions don't always point to a fatal condition or failure that ought to be exhaustively investigated and fixed. Sure. If an exception is causing some kind of error or bug - for example, the UI fails to load a channel list or EPG data - then sure it might be necessary to investigate and fix something. However most of the time with MP database related exceptions this is not the case. In this case I have yet to see any evidence that the exception you're referring to is related to the crash. I also don't see any evidence that it is causing any kind of error or bug. If you have evidence then please by all means provide it. I'm not sure what you want me to do with this information. Please understand that I'm working within a much larger context. TVE 3 uses a third party persistence framework (gentle.NET) to handle all the database related stuff. That framework is no longer being developed. Most of my time working on MP these days is spent on TVE 3.5, which has removed gentle.net in favour of Microsoft's Entity Framework. TVE 3.5 is already in use with MP2, and I'm hoping a version for MP1 will be released this year. In my opinion it is not worth my time investigating such database exceptions with TVE 3 unless they are really causing operational or reliability problems. gentle.net is going away and my belief is that these sorts of exceptions will go away with it. EF will bring its own set of challenges. Does this help you understand my perspective? :) Nope, I can't explain it. As above: TV Server doesn't interact with the database directly. Everything goes through the gentle.NET framework which I consider obsolete. Gentle.NET is responsible for converting code expressions to queries which are database engine specific. It is entirely possible that some of these queries are not as efficient as they could be. That is a common tradeoff when using a database abstraction layer. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
MP1-4502 - ChannelState.DoSetChannelStates: An unknown error occured while setting channel states
Contact us
RSS
Top
Bottom