On 7/7/05, <b class="gmail_sendername"><a href="mailto:chris@cpr.homelinux.net">chris@cpr.homelinux.net</a></b> <<a href="mailto:chris@cpr.homelinux.net">chris@cpr.homelinux.net</a>> wrote:<div><span class="gmail_quote">
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, Jul 07, 2005 at 09:08:29AM -0700, Cameron Dale wrote:<br>> How do other people deal with this? Or is this something specific to my
<br>> listings area (Vancouver, Canada)?<br><br>I have noticed that different channels have different amounts of data<br>available all the time. I use the Vancouver non-digital listings (I'm<br>in Burnaby) and have noticed that some channels always go to the end of
<br>the 14th day and others always end at 17:00 on the 12th day. Those<br>channels with short listings (A&E, DISC) were the ones that broke and<br>showed "no data" for several days. I used myth-setup to clear the
<br>listings and then ran /etc/init.d/mythfilldatabase manually, and<br>haven't had any problems since. Those channels still run a day and a<br>half behind the rest, but they do get fresh data every night.</blockquote><div>
<br>
Hey, a local! I too am in Burnaby. We should have a local MUG meetup.
:) In fact, I too use an Xbox as a frontend (which I see from another
thread that you do as well) so I guess that would make it an XMUG. ;)<br>
<br>
I am using the same listings as you, except only basic cable (<29).
I find that the stations 17,18,19,22,25,26 all stop at 17:00 on the
12th day, as you mentioned, whereas all other stations have a full 14
days.I have run myth-setup a couple of times to clear the listings and
then run mythfilldatabase manually, and it still happens to me. I don't
get fresh data every night. I'm using 0.18.1, what version are you
running? </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Perhaps the best way for me is just to write a script to clear the credits,
<br>> people, program, programgenres, and programrating tables, and then run<br>> mythfilldatabase to reload them.<br><br>You could probably just find the location where mythfilldatabase stores<br>its end-of-listings pointer and roll that back a few days every night
<br>before the normal run so that it gets 3 or 4 days worth of listings at<br>the far end of the schedule. I would expect it to fill in the holes and<br>discard the duplicates....<br><br></blockquote></div><br>
Unfortunately it looks like there is no pointer, but mythfilldatabase
just looks at the existing program data to determine what days it needs
to download data for. For me, the missing data doesn't cause my total
data for the day to drop below the threshold that mythfilldatabase uses
to determine which days to download. Perhaps your's does? <br>
<br>
In case someone else has the same problem, here's how I get around it.
I added this to my mythfilldatabasecron script before it runs
mythfilldatabase:<br>
<span><br>echo "DELETE FROM program WHERE starttime >= DATE_ADD(CURRENT_DATE(), INTERVAL 11 DAY);" | mysql mythconverg<br>echo "DELETE FROM programrating WHERE starttime >= DATE_ADD(CURRENT_DATE(), INTERVAL 11 DAY);" | mysql mythconverg
<br>echo "DELETE FROM programgenres WHERE starttime >= DATE_ADD(CURRENT_DATE(), INTERVAL 11 DAY);" | mysql mythconverg<br>echo "DELETE FROM credits WHERE starttime >= DATE_ADD(CURRENT_DATE(), INTERVAL 11 DAY);" | mysql mythconverg
<br></span><br>
This removes my program data for anything older than 11 days and then when mythfilldatabase runs, it re-gets that data.<br>
<br>
Thanks again!<br>
Cam<br>