On 11/3/05, <b class="gmail_sendername">Stuart Auchterlonie</b> <<a href="mailto:stuarta@squashedfrog.net">stuarta@squashedfrog.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 Wed, Nov 02, 2005 at 03:32:08PM -0600, Cory Zerwas wrote:<br>> ...Is there an easy way to purge the<br>> currently recorded programs out of the DB so I just have the core MythTV<br>> config, schedules, and recording groups/priorities?
<br><br>Well the main tables relating to recorded programs are<br>anything starting with recorded (recorded, recordedcredits, recordedmarkup,<br>recordedprogram, recordedrating). You could manually delete the records<br>from those tables with a bit of sql.
</blockquote><div><br>
First, thanks for the reply Stuart.<br>
I'm not a big SQL guy, at least not mySQL, but I will start reading up
and see what I can manage to accomplish. Of course, I'll be sure
to keep a backup handy in the likely event I kill the DB in some bad
way. <br>
</div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Also, if anyone has recovered an LVM 2 member disk's partition table I would<br>> appreciate hearing about that as well.
<br><br>You can create a partition table which matches what was there before<br>(easy with a single partition on the whole disk) then cross your<br>fingers and hope that the data is there. But if you get it wrong<br>your data is dead.
<br>
</blockquote></div><br>
Good idea, I was guessing I could give this a shot. The reason I
haven't done so yet is the same reason you mentioned; risk. The
drive was just a single partition so I guess I just have to create a
compatible table for LVM 2. I haven't researched any yet in this
regard, so there's some more work for me to do this weekend or next
week. (Took next week off work, yay!)<br>
What's so puzzling is why the partition table vanished, since I didn't
elect to do anything with those disks. I even had them unplugged
during the upgrade to prevent such a problem from occurring. This
leads me to wonder if there was a problem occurring just before the
upgrade that I hadn't noticed...<br>
<br>
So, in all some good information and it points to some weak areas of
knowledge for me. Thank you very much, I'm off to do a bit of
related reading. If anyone else has a tip, please drop me a
message.<br>
<br>
-Cory<br>