<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
TMS's data is only updated once per day on their server, so as long as you run a --dd-grab-all update on any given day after they do their update, you have the most-current data possible (and any further runs are wasted). <br>
</blockquote></div>
That's no longer the case. A few years ago Tribune added the mid-day updates, so the guide is updated throughout the day. A fetch before prime-time isn't a bad idea if you record shows with data that doesn't exist until the last minute.<br>
<br>
BTW, that change caused a bad side effect in which lineup and other account changes can take a few hours to propagate. We feel that more current guide data for everyone is better than quicker response for the few folks who make a lineup change. The needs of the many....<br>
</blockquote><div><br></div><div>Thanks Robert... I now feel somewhat validated, though my choice to add a pre-primetime fetch were based purely on assumption rather than any sort of evidence.<br></div><div><br></div><div>
As a representative of SD... what would you feel is the optimal path then. A grab-all or the standard grab on the nightly SD recommended schedule... plus a refresh-today just before primetime? </div><div><br></div><div>
Also I have often wondered why mythfilldatabase needs to do so much work to update a schedule when there are few changes. I was curious if SD maintains a "last updated date/time" field within the data it stores. It would be cool if mythfilldatabase could request only updates since the last run eg "mythfilldatabase --updates-since <date-time-of-last-run>. I'm not sure if this would increase or decrease the load on the SD servers (though it would certainly save bandwidth).</div>
</div></div></div>