[mythtv-users] why change db stuff with every version change?
evuraan at gmail.com
Thu Nov 26 01:08:47 UTC 2009
Like Dale, I also have multiple frontends and one just b/e. And one of
the F/E went with karmic koala (ubuntu 9.10, 0.22) and it can no
longer work with my hardy (8.04) backend since my b/e is 0.21.
an annoyance indeed.
i am not yet ready to upgrade my backend, and my other f/e clients to 0.22.
i am not sure whether i can bring just the b/e db schema upto the
"mark for 0.22 f/e client" while leaving the ver as it is at 0.21. is
this even possible? any guidance will be appreciated. (pls note, i
will have 0.21, 0.22 f/e clients)
2009/11/25 Dale Pontius <DEPontius at edgehp.net>:
> Robin Hill wrote:
>> What's preventing you updating all the backends/frontends anyway? It's
>> not like there's embedded systems which will need replacing at large
>> cost, it's just a software update.
> Most of my Myth machines are Gentoo, But there are 2 Ubuntu machines in
> the house. As far as I can tell, neither has released 0.22 to "stable"
> yet, but I've no doubt that they will do so at different times. As of
> now, I just plan to have some time when the Ubuntu machines can't run
> the Myth frontend.
> I don't see that as a big problem, just a minor annoyance.
> Right now I'm far more concerned about the database conversion. At
> various times I've come across Gentoo messages telling me to do this or
> that to my database and/or /etc/mysql/my.cnf. I know that at least once
> I've had to drop and reload the database. Right now I'm fearing that
> I've got a bad case of "partial corruption", as some have put it, and
> that it won't show up until the first time I fire up 0.22.
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users