Database issue?

[Brendon 119]

One of my users just reported this issue to me and thought i'd better post something here after confirming it was happening.

User was adding the tv show '1883' to their favourites and for some reason kept getting the movie 'Garage Sale Mystery: The Novel Murders' added as well, removing one would remove the other so she sent me a text advising what was happening and upon checking this is what i found;

The tvdbid for 1883 and the tmdbid for Garage Sale Mystery: The Novel Murders are the same '396390', if i remove the id from one it vanishes from favourites the other stays and vice versa. Why are these two different fields colliding?? Is there are a rather nasty conflict going on somewhere? i do not see why these two fields are getting mixed up but i have had to remove the tmdbid from Garage Mysteries and lock the fields to temporarily fix it. 

[Happy2Play 9783]

Yes there would appear to be a conflict as then both get the same userdatakey here in the database. @Luke

So the question becomes how are Favorite items matched as 396390 will apply to two different items per different providers? (Sort of surprised this has not come up before)

{
        "Key": "396390",
        "PlaybackPositionTicks": 0,
        "PlayCount": 0,
        "IsFavorite": true,
        "HideFromResume": false,
        "Played": false,
        "RatingLastModified": "2022-12-04T02:07:24.0000000Z",
        "PlaystateLastModified": "2022-12-04T00:52:52.0000000Z"
    }

 

So currently any items with like providerids will be linked for Favorites is my understanding.  But devs will have to confirm. @ebr

Edited December 5, 2022 by Happy2Play

[Luke 42085]

Hi, yes this kind of thing should be rare but it's something we'll need to look at addressing. Thanks.

[Happy2Play 9783]

Appears to only apply to different providers having the same number as same provider with same number (TV/Movie) does not do this.

So same id via TMDB and TVDB will be linked.

 

[Brendon 119]

Oh you found another @Happy2Play, i figured it would be a rare occurence given the size of my libraries and having never seen this before, didn't expect another to be found so quick. I hadn't had the time to dig into the db over the weekend when i first reported but found the conflict by comparing the .nfo's  after my user sent me a text about it and on the off-chance it was a bigger issue then i thought, wanted it known by you guys.

As i pointed out the simple work around for anyone else coming across this is to remove the duplicate id number from one or the other and lock that one, will stop it until @Luke comes up with a fix.

[Happy2Play 9783]

@Brendon A workaround would appear to be modifying the id.

example I went to tmdb link for Garage Sale Mystery: The Novel Murders and Hardcastle and McCormick and looked at the url and applied it instead of just id breaking the link.

396390-garage-sale-mystery-the-novel-murders

1271-hardcastle-and-mccormick

Does not appear to break anything else in my limited testing.