<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 9:17 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.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">On 08/21/2013 09:10 AM, John Drescher wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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>
</blockquote>
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>
</blockquote>
<br></div>
Just make sure before you start poking raw data in the database you read all of the MythTV source code and understand all of the data constraints and requirements, as they aren't expressed in the database.</blockquote>
<div><br></div><div>I hear you. The good thing for this test is that I have daily backups of the db and the show I was testing with it would not be the end of the world if I deleted the whole set for that since its on 4 to 6 different channels it would get rerecorded in month or so..<br>
<br></div><div>John <br></div></div></div></div>