[mythtv-users] new recordings missing database fields after R5A22 upgrade

[Michael T. Dean]

Byron Poland wrote:

>On 10/26/05, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>  
>
>>Byron Poland wrote:
>>
>>>Here is the relevant part of my backend log on on startup:
>>>
>>>2005-10-26 15:02:15.804 Using runtime prefix = /usr
>>>QSettings::sync: filename is null/empty
>>>2005-10-26 15:02:15.953 New DB connection, total: 1
>>>2005-10-26 15:02:15.991 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.
>>>QSettings::sync: filename is null/empty
>>>2005-10-26 15:02:16.005 New DB connection, total: 2
>>>2005-10-26 15:02:16.013 Database Schema upgrade complete, unlocking.
>>>
>>>no errors... it does do this on every start of the backend though.
>>>
>>What does
>>
>>SELECT data FROM settings WHERE value = 'DBSchemaVer';
>>
>>give?
>>    
>>
>mysql> SELECT data FROM settings WHERE value = 'DBSchemaVer';
>+------+
>| data |
>+------+
>| 1099 |
>+------+
>1 row in set (0.00 sec)
>  
>
And it's still trying to upgrade the database on every backend restart?  
(You keep seeing the, "Setting Lock for Database Schema upgrade," 
message?)  Were there lines:

Current Schema Version: 109X
Newest Schema Version : 1099

above the, "Setting lock," message in the log?

Mike