[mythtv-users] DB Schema update 1261: broken duplicate detection with historic non-DD data
Michael T. Dean
mtdean at thirdcontact.com
Tue Apr 21 13:43:28 UTC 2015
On 04/21/2015 09:37 AM, Michael T. Dean wrote:
> So is there some way you corrupted your database and removed that
> setting? I.e. if you don't properly restore the database--and do
> something broken, like restoring only certain tables (where doing so
> is not only broken, but out-right dangerous if the database version
> isn't correct/up-to-date) to "clean up" the database--you could end up
> running that code again, even though it was already run in 2007.
> Similarly, if you "cleaned up" the database by removing old settings
> values that you thought you didn't need, you could end up running that
> code again.
And, FWIW, this is exactly why I move that code from a "run every time
unless there's a setting value that says not to do so" code block to a
proper DB update.
Mike
More information about the mythtv-users
mailing list