[mythtv-users] Upcoming recordings gone

[Daryl McDonald]

On Thu, Oct 28, 2021 at 4:57 PM Daryl McDonald <darylangela at gmail.com>
wrote:

> Thanks Bill, that rendered an empty set, Yeah! I'm going to reboot and
> have a look.
>
> On Thu, Oct 28, 2021 at 3:50 PM Bill Meek <keemllib at gmail.com> wrote:
>
>> On 10/28/21 2:38 PM, Daryl McDonald wrote:
>> >
>> >
>> >
>> >
>> >     >     >
>> >     >     >         mysql> SELECT chanid,recpriority FROM channel WHERE
>> recpriority != 0 ORDER BY chanid;
>> >     >     >         +--------+-------------+
>> >     >     >         | chanid | recpriority |
>> >     >     >         +--------+-------------+
>> >     >     >         |   1061 |          -3 |
>> >     >     >         |   1161 |          -2 |
>> >     >     >         |   1171 |          -1 |
>> >     >     >         |   1301 |          -5 |
>> >     >     >         +--------+-------------+
>> >     >     >         4 rows in set (0.00 sec)
>> >     >
>> >     >     You can follow this on:
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>
>> >     <https://forum.mythtv.org/viewtopic.php?f=36&t=4628 <
>> https://forum.mythtv.org/viewtopic.php?f=36&t=4628>>
>> >     >
>> >     >     You'll see that a single negative recpriority will cause the
>> SQL error pasted
>> >     >     earlier. The issue is still open
>> >     On 10/28/21 6:08 AM, Daryl McDonald wrote:
>> >     > Thanks Bill, halfway there, I was able to neutralize the priority
>> factor on two of the four that showed from the query. The other two do not
>> >     > show up in frontend settings because I deleted those channels.
>> How would I go about making that change from mysql?
>> >
>> >     This is a safe way, just change the chanid:
>> >
>> >       mysql --user=mythtv --password --execute="UPDATE channel SET
>> recpriority=0 WHERE chanid=98765 LIMIT 1" mythconverg
>> >
>> >     --
>> >     Bill
>> >
>> > The above command does not look like a mysql command because it does
>> not end with a semicolon.
>>
>> It was intended to be run from the shell command line, you don't need to
>> enter mysql.
>>
>> > This shows the two remaining:
>> > mysql> SELECT chanid,recpriority FROM channel WHERE recpriority != 0
>> ORDER BY chanid;
>> > +--------+-------------+
>> > | chanid | recpriority |
>> > +--------+-------------+
>> > |   1061 |          -3 |
>> > |   1301 |          -5 |
>> > +--------+-------------+
>> > 2 rows in set (0.01 sec)
>> >
>> > I just want to be certain before I mess with mysql, I don't see how
>> your command, Bill, targets my remaining channel priorities?
>> > Do I need to make substitutes in the command, like the actual password?
>>
>>
>> In your case, you'd run the above twice, replacing 98765 with 1061 and
>> again with 1301.
>> There are other ways to do it, but this works.
>>
>> The actual fix was just tested and pushed for master and fixes/31, by the
>> way.
>> (by gigem)
>>
>> --
>> Bill
>>
>>
 Still no upcoming recordings? I just upgraded and nothing for myth or
mysql that I saw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20211028/11064b3e/attachment.htm>