[mythtv] an idea from ruby on rails

Chris Pinkham cpinkham at bc2va.org
Sat Jan 26 08:30:11 UTC 2008

* On Fri Jan 25, 2008 at 02:00:08PM -0500, Michael T. Dean wrote:
> 0.20-0.21 will still work).  Heh.  I actually mentioned the Backup
> storage group way back in September--
> http://www.gossamer-threads.com/lists/mythtv/users/288037#288037 --and
> even then, I was way "late" on the patch.  I really need to get this done.

Chalk one up to my failing memory.... :)

> > We can make a method
> > in the Storage Groups class to list all groups available for recordings
> > and eliminate some of these special groups.
> Yeah.  Wasn't sure whether they should be eliminated from the scheduled
> recording editor's selections or left (if the user /wants/ recordings in
> DB Backup or Thumbnails or ...).  I was planning on asking you in IRC. 

I added a helper function for this tonight.  Just add special group names
in the "WHERE groupname NOT IN ('blah', 'blah'" SQL and they won't show
up in the scheduled recording editor.

> without any new settings! :)  I also planned to allow backup rotation,
> but can't think of a way to do that without a setting(s) (MaxDBBackups
> or MaxDBBackupStorage or MaxDBBackupAge or ...).  Do you think that's
> better handled externally, with settings, as a special configuration for
> the special DB Backups storage group, or any other suggestions for it?

I'd leave it external, not in the Storage Group area since the settings
would apply whether the user created a special SG or not.  I guess once
we see what the MythVideo SG settings look like, then it may make sense
to just put these on the DB Backups SG settings page.  If the user didn't
setup a specific backups SG, then the defaults are used.

> itself--is the easy part.  Making the changes to the housekeeper (to
> allow the job to run only if no recordings/LiveTV are in progress and if
> no recordings are about to start; and to allow a "run anyway," i.e. for
> mfdb; and ...) is a bit more complex (especially since I'd like to make
> the housekeeper changes/support code usable for the jobqueue stuff,
> too).

It might be a good idea to also run a backup before any schema upgrade.
This might not be possible if running mythfrontend, but should be with
mythbackend and mythtv-setup (when run on a backend).


More information about the mythtv-dev mailing list