[mythtv-users] Unable to See Recordings in Storage Group After Upgrade to 0.28.
Ian Barton
lists at wilkesley.net
Sun Aug 14 10:47:57 UTC 2016
On Wed, May 11, 2016 at 06:11:09PM +0100, lists at wilkesley.net wrote:
> On 2016-04-24 14:19, Bill Meek wrote:
> >On 04/24/2016 02:55 AM, lists at wilkesley.net wrote:
> >>On 2016-04-23 16:26, Bill Meek wrote:
> >>>On 04/23/2016 05:36 AM, lists at wilkesley.net wrote:
> >>>>I am upgrading 0.27 to 0.28 by simply upgrading the Arch package.
> >>>>Nothing in respect of file permissions, mount points, users had
> >>>>changed
> >>>>from what works fine in 0.27.
> >>>
> >>>Ian,
> >>>
> >>>Off list, I hope. If this pans out, I'll go back
> >>>on. And I'll be off the air while I do the 16.04
> >>>upgrade on my office PC.
> >>>
> >>>Do you use recording groups? Asking because there
> >>>was a change in 0.28 related to them. Mine, all
> >>>one of them, converted A-OK.
> >>>
> >>>Would be interesting to know that the values
> >>>look sane (sum of the recgroupids=recgroups=
> >>>total recordings.) I don't recall a GUI or API
> >>>to edit them yet.
> >>>
> >>>http://pastebin.com/4d4bnPGr (I added an error
> >>>in my DB, but it *doesn't* prevent the
> >>>display of the recording.)
> >>
> >>Yes I use recording groups a lot. Partly so I can assign different user
> >>jobs based on the recording group. I'll set up a backend on a different
> >>computer using 0.27 and then upgrade it to 0.28 and see what happens to
> >>the recording groups. I'll see if I can find out how recording groups
> >>changed in 0.28.
> >>
> >
> >Hi,
> >
> >I don't want to send you on a wild goose chase. The change is to add
> >a new column called recgroupid to the recorded table. That id is an
> >index into a new recgroups table. You should have as many entries
> >in the new recgroups as you have old recgroup names (plus the special
> >Default, LiveTV and Deleted ones.)
> >
> >In 0.28, the old recgroup column still exists.
> >
> >Given your description of the issue, I started looking at the DB
> >upgrades that were done since 0.27 and that was the closest thing
> >that I could come up with. *Could be a complete red herring though*.
> >
> >I wasn't able to duplicate the issue you're seeing with my single
> >recgroup.
> >
> >SELECT * from recgroups;
> >+------------+----------+----------------+----------+---------+
> >| recgroupid | recgroup | displayname | password | special |
> >+------------+----------+----------------+----------+---------+
> >| 1 | Default | | | 1 |
> >| 2 | LiveTV | | | 1 |
> >| 3 | Deleted | | | 1 |
> >| 4 | TOH | This Old House | hot | 0 |
> >+------------+----------+----------------+----------+---------+
>
> Apologies, first reply went to your email, rather than the list. I'll stick
> to using mutt instead of this fance web thingie in future:)
>
> Just got time to have another look at this:
>
> SELECT * from recgroups;
>
> +------------+----------+-------------+----------+---------+
> | recgroupid | recgroup | displayname | password | special |
> +------------+----------+-------------+----------+---------+
> | 1 | Default | | | 1 |
> | 2 | LiveTV | | | 1 |
> | 3 | Deleted | | | 1 |
> | 4 | nokia | nokia | | 0 |
> | 5 | h264 | h264 | | 0 |
> | 6 | radio | radio | | 0 |
> | 7 | ipod | ipod | | 0 |
> | 8 | android | android | | 0 |
> | 9 | soaps | soaps | | 0 |
> | 10 | archos | archos | | 0 |
> | 11 | cowon | cowon | | 0 |
> +------------+----------+-------------+----------+---------+
>
> Now:
>
> SELECT * FROM `recorded` WHERE recgroupid=8
> Showing rows 0 - 24 (231 total, Query took 0.0005 seconds.)
>
> Which looks correct. However, the front end is only showing 14 recordings
> out of 231 from the android group.
Just in case anyone else has this problem, the latest Arch package
1:0.28-6 seems to have fixed the problem. I was forced to upgrade from
0.27 because of various dependency problems stopped the backend
working. However, this time the upgrade went smoothly and I can now
see all my recordings!
Ian.
More information about the mythtv-users
mailing list