> > I had the same problem and took those steps but those colums never got > > created on mine (not sure why probably a fluke) can someone give me the > > details of those columns to I can create them correctly? > > The point is that if it didn't upgrade to 1066 or whatever, backing > out the partial changes means that it will try again the next > time and should succeed. > > That said, if you "fluke" caused the version number to increment > without having these changes you can look in the file dbcheck.cpp > to find the SQL lines to add them.
I just restored mythconverg from a mysqldump I did prior to installing 0.17 and it worked successfully on the second try. I believe the fluke I experienced was both myth frontend and backend running at the same time, or something like that... maybe they where both doing BD changes, and that didn't work so well. :) Used your advice and just let mythbackend do the updates, and it was fine. In my opinion, part of the auto-db-update process should be backing up the DB before it touches it. Seems like the problem could be ugly if someone didn't have a backup?... Although, I'm not sure how intensive the db changes are and what things could go wrong. I just prefer to be safer than sorrier. Then again, I suppose where not talking mission critical data... ;) -Kenneth
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
