[mythtv-users] URGENT: No TV shows after 0.21 upgrade :-(

[Michael T. Dean]

On 03/27/2008 05:32 AM, Warpme wrote:
> I just upgrade form r5f27 to 0.21 via 0.21-fixes compilation on r5f27
> system.
> Well - at first look thing went well - but closer examination shows
> issue with accessing existing tv shows.
> FE shows my recordings groups and no shows in group OK - but entering
> particular group list shows empty list.
>
> Going into backend log shows following error: 
...
> 2008-03-27 10:07:08.609 DB Error (ProgramList::FromRecorded):
> Query was:
> SELECT
> recorded.chanid,recorded.starttime,recorded.endtime,recorded.title,recorded.subtitle,recorded.description,recorded.hostname,channum,name,callsign,commflagged,cutlist,recorded.autoexpire,editing,bookmark,recorded.category,recorded.recgroup,record.dupin,record.dupmethod,recorded.recordid,channel.outputfilters,recorded.seriesid,recorded.programid,recorded.filesize,
> recorded.lastmodified, recorded.findid, recorded.originalairdate,
> recorded.playgroup, recorded.basename, recorded.progstart,
> recorded.progend, recorded.stars, recordedprogram.audioprop+0,
> recordedprogram.videoprop+0, recordedprogram.subtitletypes+0,
> transcoded, recorded.recpriority, watched, recorded.preserve,
> recorded.storagegroup FROM recorded LEFT JOIN record ON
> recorded.recordid = record.recordid LEFT JOIN channel ON
> recorded.chanid = channel.chanid LEFT JOIN recordedprogram ON  (
> recorded.chanid = recordedprogram.chanid AND   recorded.progstart =
> recordedprogram.starttime ) WHERE ( recorded.deletepending = 0
> OR         DATE_ADD(recorded.lastmodified, INTERVAL 5 MINUTE) <=
> NOW()       ) ORDER BY recorded.starttime
> DESC,atsc_major_chan,atsc_minor_chan,channum,callsign
> Driver error was [2/1054]:
> QMYSQL3: Unable to execute query
> Database error was:
> Unknown column 'watched' in 'field list' 

Restore the backup from before the upgrade (if you didn't do a backup,
one was created automatically before the database upgrade attempt). 
Then run:

mythtv-setup 2>&1 | tee ~/setup.log

and post setup.log so we can tell you what is broken, so we can tell you
how to fix it.  Otherwise, you're likely to have more problems than you
realize, and they'll continue to plague you as they occasionally surface
over time as you're using your system with a broken database.

Mike