On Fri, Feb 22, 2008 at 6:51 AM, Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 02/22/2008 01:27 AM, Michael T. Dean wrote:<br>
>>>> I have a similar question - but less radical. If I want to leave<br>
>>>> 'svn' and go to 0.21-fixes - I assume the two databases are<br>
>>>> currently compatible (same schema).<br>
</div><div class="Ih2E3d">> Check currentDatabaseVersion in mythtv/libs/libmythtv/dbcheck.cpp in the<br>
> -fixes branch and make sure it's greater than or equal to the version<br>
> you're currently using. The schema version number appears in the<br>
> automatic backup you get (in trunk/0.21-fixes) before a schema change<br>
> (i.e. mythconverg-<schemaver>-<datetime>.sql (perhaps .gz, too)).<br>
<br>
</div>Also should have mentioned that 0.21-fixes/trunk will try to do the<br>
right thing. I.e. if you have an older schema version than required and<br>
start mythfrontend, it will tell you start mythbackend or mythtv-setup<br>
to upgrade your DB (or use the -u flag to allow mythfrontend to upgrade<br>
the schema). If you have a newer schema version than required,<br>
mythtv-setup/mythbackend/mythfrontend will exit with an error saying you<br>
need to upgrade MythTV.<br>
<br>
In other words, though it doesn't completely keep you from shooting<br>
yourself in the foot (I'm leaving out instructions for how to do so),<br>
with the automatic backup and the schema version checks/refusal to run<br>
with the wrong schema version, Myth now provides steel-toe boots to help<br>
minimize the damage you'll do.</blockquote><div><br>Thanks Mike, <br><br>I've double checkd in dbcheck.cpp in both versions (0.21 fixes and trunk) that I've checked out and both are on 1212 - so I'll give it a try. I've been using trunk (very successfully) for over a year, but thought it might be a good time to take a breather and use a stable release for a while. It seemed like the perfect time to jump off the trunk treadmill, and I was worried that by the time the official release happened trunk may well be on a newer schema and I would have lost my window. Again - I'm assuming (always a bad thing) that there should be no other major 'gotchas' going from trunk to fixes (given both are on 1212).<br>
<br>I'm pretty sure I'll miss the neat features that keep being added to trunk, and like a crack addict will come back to trunk within a month after release though!<br><br>Best regards,<br>Nick<br></div></div>