[mythtv-users] recordid not being set in recorded table in Myth v32

Stephen Worthington stephen_agent at jsw.gen.nz
Tue May 10 10:34:22 UTC 2022


On Tue, 10 May 2022 10:08:24 +0000, you wrote:


>Hi John,
>
>
>
>Thanks for your Input, but recordedid is a different value to recordid:
>
>
>
>mysql> select title, starttime, recordid, recordedid from recorded where recordid = 0 order by starttime asc;
>
>+---------------------------+---------------------+----------+------------+
>
>| title                     | starttime           | recordid | recordedid |
>
>+---------------------------+---------------------+----------+------------+
>
>| Top Gear                  | 2022-05-09 07:00:00 |        0 |      31108 |
>
>| This Week's Magic Singles | 2022-05-09 19:55:33 |        0 |      31110 |
>
>| Non-Stop Magic Hits       | 2022-05-10 05:03:20 |        0 |      31114 |
>
>| Non-Stop Magic Hits       | 2022-05-10 05:52:58 |        0 |      31116 |
>
>+---------------------------+---------------------+----------+------------+
>
>4 rows in set (0.00 sec)
>
>
>
>
>
>
>
>In my case, any new recordings seem to have a value of 0 for recordid, the value for recordedid is OK. At the moment I'm updating the field manually, so that my Mythodcaster process will work, but that's not ideal.
>
>
>
>Regards,
>
>Dave.

The recordedid column is the index for the recorded table.  It is
autoincremented for each new recording.  The recordid column is the
index for the record table (the recording rules).  It is
autoincremented for the creation of each new recording rule.  Each row
in the recorded table should have the recordid column set to the
recordid of the recording rule in the record table that created that
recording.


More information about the mythtv-users mailing list