[mythtv-users] Please Wait...

[Brent Bolin]

On Mon, Apr 26, 2010 at 2:20 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 04/26/2010 03:06 PM, Brent Bolin wrote:
>>
>> On Mon, Apr 26, 2010 at 11:20 AM, Michael T. Dean wrote:
>>
>>>
>>> On 04/26/2010 08:26 AM, Brent Bolin wrote:
>>>
>>>>
>>>> No hard drives are spinning up.  The back end runs 24x7 with no power
>>>> management.
>>>>
>>>> I was thinking it's just the front end making an SQL connection.
>>>>
>>>
>>> Update to current 0.23-fixes
>>
>> Can a full mysql backup of .22-fixes be restored to .23-fixes to keep user
>> data?
>>
>
> I don't understand the question.  Basically, for an upgrade, you should let
> MythTV 0.23-fixes upgrade your 0.22-fixes database to the proper schema
> version.  If you're moving your database from one distro install to another
> (or upgrading MySQL server), you should do a full restore of a 0.22-fixes
> database /before/ running any MythTV programs and use mythtv-setup
> (preferred, or mythbackend for the lazy people who are feeling lucky) to
> automatically upgrade it to the 0.23-fixes schema.
>
> There's /absolutely/ no reason to do a partial restore of your database
> unless you've actually broken the database schema.  A partial restore can
> never be used across differing schema versions.
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

Not sure what I was thinking.  Not use to fully supported upgrade paths.

This is on Mythbuntu.  So what your saying is if I change within myth
control center myth version 22 to 23 I should be able to just sit back
and hang on for the ride? :)

I don't have any intension of upgrading at the moment.  Just want to
know the procedure.