[mythtv] Database upgrade failure

[John Pilkington]

On 24/01/2022 17:56, David Hampton via mythtv-dev wrote:
> On Mon, 2022-01-24 at 17:38 +0000, Gary Buhrmaster wrote:
>> On Mon, Jan 24, 2022 at 5:22 PM Gary Buhrmaster
>> <gary.buhrmaster at gmail.com> wrote:
>> I just noticed another issue.  The sportslisting
>> table uses a foreign key.  And MYISAM does
>> not support foreign keys.
>>
>> TTBOMK, the MythTV project as historically
>> avoided using foreign keys (preferring to
>> implement the business logic in the code,
>> and any cleanups, including inconsistencies,
>> to be in the housekeeping codes) in order
>> to be database independent.
> 
> I think I can just drop the FOREIGN_KEY statement, as the code already
> contains the following constraint in the select statement(1):
> 
>      "INNER JOIN sportsapi api ON sl.api = api.id"
> 
> I only have a passing familiarity with sql, so I'd love to hear from
> anyone with more experience if this is a correct solution.
> 
> Thanks.
> 
> David
> 
> 1) From programs/mythbackend/recordingextender.cpp:1153.
> 
I can't comment on that; but after a fairly protracted session with yum 
erase --nodeps, yum install and myththconverg_restore.pl I appear to be 
back to a working system  - I hope :-)

I still have the new rpms;  good to know that they will build and are 
installable.

John