[mythtv-users] Slow MySQL query after delete

[Chris Pinkham]

* On Wed Dec 05, 2007 at 06:02:48AM -0800, Yeechang Lee wrote:
> What about deleting original recording files after transcoding? Does
> 0.21 use the same slow-delete code for this purpose, or do you have
> the system save original files and delete them manually at non-busy
> times, or do you never transcode?

No, these files are no longer under Myth's control (since mythtranscode
renamed them), so mythtranscode deletes them with a simple call
to unlink().  We din't want to create a command on the backend
to allow deleting any file, so this has to be this way for now.

Perhaps when I get around to finishing my multiple-file-per-recording
patch, then the backend can do this actual deletion.  Or maybe someone
will get fed up with it enough to add slow-deletion code to
mythtranscode. :)  I run all my transcoding jobs after midnight,
so it doesn't bother me too much right now.

--
Chris