Reply to thread

Message

I'm glad you haven't been bit by sqllite3. After months of trying to work around it's problems I gave up on it entirely when developing my EPG/recording system. I had to use it to get into the tvseries database but between the memory issues and nonsql conformance it wasn't worth continuing. Ended up scraping IMDB myself for the information. I'd been using mssql in MP1 for the last 5 or 6 years (having given up on MySQL because of performance issues there as well) MSSQL 2008 r2 +, 2012 and 2016 have all been rock solid low overhead and easy to maintain. looking at MP from the outside and trying to get things like EPG to work with bad free sources means needing to combine data. if sqllite is the only database used that pretty much puts paid to me being able to access/fix channel lists or do any of the predictive show scheduling I've been doing. at this point I've been able to keep all processing away from MP so I impact it as little as possible. if I need to move the design to a plugin to access the required fields then performance becomes more of a concern.

Thanks for your insight. I guess my next step is to investigate plugins.. both for sqlserver access and my end user scheduling stuff.

<blockquote data-quote="gpnash" data-source="post: 1201501" data-attributes="member: 151666">I'm glad you haven't been bit by sqllite3. After months of trying to work around it's problems I gave up on it entirely when developing my EPG/recording system.&nbsp; I had to use it to get into the tvseries database but between the memory issues and nonsql conformance it wasn't worth continuing.&nbsp; Ended up scraping IMDB myself for the information.&nbsp; I'd been using mssql in MP1 for the last 5 or 6 years (having given up on MySQL because of performance issues there as well)&nbsp; MSSQL 2008 r2 +, 2012 and 2016 have all been rock solid low overhead and easy to maintain. looking at MP from the outside and trying to get things like EPG to work with bad free sources means needing to combine data. if sqllite is the only database used that pretty much puts paid to me being able to access/fix channel lists or do any of the predictive show scheduling I've been doing.&nbsp; at this point I've been able to keep all processing away from MP so I impact it as little as possible.&nbsp; if I need to move the design to a plugin to access the required fields then performance becomes more of a concern.Thanks for your insight.&nbsp; I guess my next step is to investigate plugins.. both for sqlserver access and my end user scheduling stuff.</blockquote>

[QUOTE="gpnash, post: 1201501, member: 151666"] I'm glad you haven't been bit by sqllite3. After months of trying to work around it's problems I gave up on it entirely when developing my EPG/recording system. I had to use it to get into the tvseries database but between the memory issues and nonsql conformance it wasn't worth continuing. Ended up scraping IMDB myself for the information. I'd been using mssql in MP1 for the last 5 or 6 years (having given up on MySQL because of performance issues there as well) MSSQL 2008 r2 +, 2012 and 2016 have all been rock solid low overhead and easy to maintain. looking at MP from the outside and trying to get things like EPG to work with bad free sources means needing to combine data. if sqllite is the only database used that pretty much puts paid to me being able to access/fix channel lists or do any of the predictive show scheduling I've been doing. at this point I've been able to keep all processing away from MP so I impact it as little as possible. if I need to move the design to a plugin to access the required fields then performance becomes more of a concern. Thanks for your insight. I guess my next step is to investigate plugins.. both for sqlserver access and my end user scheduling stuff. [/QUOTE]