You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This probably affects other areas to, but I noticed this in the charts page.
Example:
Movie: Iron Man 3
Section: Movies (ratingKey: 7675)
Section: 3d Movies (ratingKey: 8787)
The history will show a play count of lets say 11, however the linked item is only for rating key 7675, which only has one play. The rest of the plays were in 8787.
I was playing around with it, and it looks like we might want to pass info.php?id=7675|8787 and handle multiple rating keys for the same title. I have a working example for passing multiple keys, but I haven't worked on actually obtaining the multiple keys before being passed. You might have better ideas since it's your code :)
The text was updated successfully, but these errors were encountered:
The problem lies in the original grouping query to the database, to order properly I think it would need to do sub-queries which would slow down an already slow query even further. It's come up elsewhere though so I might look into how feasible it is.
This probably affects other areas to, but I noticed this in the charts page.
Example:
Movie: Iron Man 3
Section: Movies (ratingKey: 7675)
Section: 3d Movies (ratingKey: 8787)
The history will show a play count of lets say 11, however the linked item is only for rating key 7675, which only has one play. The rest of the plays were in 8787.
I was playing around with it, and it looks like we might want to pass info.php?id=7675|8787 and handle multiple rating keys for the same title. I have a working example for passing multiple keys, but I haven't worked on actually obtaining the multiple keys before being passed. You might have better ideas since it's your code :)
The text was updated successfully, but these errors were encountered: