<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 10:15 AM, Joseph Fry <span dir="ltr"><<a href="mailto:joe@thefrys.com" target="_blank">joe@thefrys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">>>> The beauty is, that everything you do in the menu can be accomplished<br>
>>> by editing the database. I don't know what exactly "allow this<br>
>>> episode to rerecord" does... but there is no doubt in my mind that you<br>
>>> could reproduce this in scale with a few lines of SQL.<br>
>><br>
>> This would be a good approach for me. I am a programmer (actually these<br>
>> days I program in Qt) but sql update queries will be pretty easy for me<br>
>> provided I find the right place to update..<br>
><br>
><br>
> Just make sure before you start poking raw data in the database you read all<br>
> of the MythTV source code and understand all of the data constraints and<br>
> requirements, as they aren't expressed in the database.<br>
<br>
>> Yesterday I tried deleting all of the 200+ items in oldrecorded for a<br>
>> particular show expecting it forget the old. That did not help. I had to<br>
>> still force recording via the upcoming recordings screen of mythweb.<br>
<br>
</div>Did you trigger a scheduler run afterward?<br></blockquote><div><br></div><div>Yes a few times. That did not help..<br><br></div><div>John </div></div></div></div>