Recent tab can become out of sync with the recent database, causing it not work properly

[Victor Thompson]

Note: I'm running the refactor series, so this may only be an issue there.

It seems that sometimes the recent tab can become out of sync with the data in the database. This maybe somewhat difficult to reproduce, but the following should sometimes cause it. I believe it might have something to do with deleting playlists:

1. Play a couple of albums so that they are in the recent tab.
2. Create one or more playlists
3. Add songs to these playlists
4. Play each playlist created in step #2
5. Navigate to the Recent tab to ensure the playlists are listed
6. Play one of the albums listed in the recent tab
7. Navigate to the Playlists tab and delete the playlists created in step #2
8. Navigate to the Recent tab and attempt to click on each item listed

Actual results: Some of the items do not do anything when clicked/tapped and cause an error in the console.

Expected results: Each item listed in the Recent tab should work as expected.

The output when an item fails to be clickable is the following:

file:///opt/click.ubuntu.com/com.ubuntu.music/2.0.856/app/ui/Recent.qml:85: TypeError: Cannot read property 'type' of null

I've attached the screenshot of the contents of the Recent tab, one thing to note is that they do not match the contents of the recent database table, which is the following:

"2015-05-09T12:22:06.514" "Coco" "album"
"2015-05-09T12:23:54.251" "A" "playlist"
"2015-05-09T12:24:00.246" "B" "playlist"
"2015-05-09T12:24:07.896" "Alpha Numeric" "album"

[Victor Thompson (vthompson)]

Adding the application log.