[mythtv-users] database error before every recording starts on 0.19-fixes svn revision 9709.

[Khanh Tran]

On 4/14/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> On 04/14/2006 09:19 AM, Khanh Tran wrote:
> > I recently went to svn 9709 and now I'm getting database errors when a
> > recording starts:
> >
> > 2006-04-14 08:30:02.579 DB Error (Copy program data on record):
> > Query was:
> > REPLACE INTO recordedprogram SELECT * from program WHERE chanid = '2123' AND sta
> > rttime = '2006-04-14T08:30:00';
> > Driver error was [2/1136]:
> > QMYSQL3: Unable to execute query
> > Database error was:
> > Column count doesn't match value count at row 1
> >
> > 2006-04-14 08:30:02.621 TVRec(1): Changing from None to RecordingOnly
>
> Your subject says you're running 0.19-fixes and the error would occur
> there if and only if you had previously run SVN head (somewhere between
> r9668 but before r9686) and then went back to 0.19-fixes...
>
> If you have DBSchemaVer 1136, that's exactly what happened:
>
> mysql -umythtv -p mythconverg -e "SELECT * FROM settings WHERE value =
> 'DBSchemaVer';"
>
> In SVN head, [9686] fixes the issue (
> http://www.gossamer-threads.com/lists/mythtv/commits/197056#197056 ) .
>
> Are you absolutely sure /all/ your Myth systems (frontends and backends)
> are using 0.19-fixes?  At some point, you've run a non-fixes SVN head
> version of Myth.  Running different versions of Myth frontends/backends
> and "downgrading" your Myth system are not supported.
>
> If you want to stay on 0.19-fixes, how old is your last 0.19-fixes
> database backup?
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

I probably should have said I'm running 9707 from the fixes branch.  I
went back and forth on a couple revisions for a frontend-only, but
only forward on the backend. The output of my master backend shows the
Current Schema is 1136 and the Newest Schema is 1123 as quoted below. 
I'm assuming my database never upgraded?  DBSchemaVer is 1136 in my
database.  Should I manually do "ALTER TABLE recordedprogram ADD
listingsource INT NOT NULL default '0';"?


2006-04-13 09:02:22.210 Current Schema Version: 1136
2006-04-13 09:02:22.225 Newest Schema Version : 1123
2006-04-13 09:02:22.237 Setting Lock for Database Schema upgrade. If
you see a long pause here it means the Schema is already locked and is
being upgraded by another Myth process.
2006-04-13 09:02:22.276 Database Schema upgrade complete, unlocking.
2006-04-13 19:59:30.960 Current Schema Version: 1136
2006-04-13 19:59:30.961 Newest Schema Version : 1123
2006-04-13 19:59:30.965 Setting Lock for Database Schema upgrade. If
you see a long pause here it means the Schema is already locked and is
being upgraded by another Myth process.
2006-04-13 19:59:30.970 Database Schema upgrade complete, unlocking.