Sprijin Bază de date filme (The Movie Database)
Sprijin → Sprijin API
Suggestion: 'last_updated' timestamp in (movie|tv|person)/{id}/changes call.
postat de către Sourav BiswasSTAFFMOD pe data de 23 iunie 2017 la ora 10:54AM
Hello,
I think the mentioned field will come handy to check periodically if there is any new changes. Presently it only provides last 24 hours info or data of 14 days window. In some situation which is not sufficient. A summary of changes within a longer window will also be helpful I guess for some situations.
- Sourav
Răspuns de Travis Bell
pe data de 26 iunie 2017 la ora 10:23AM
Hi Sourav,
When you say "last updated" are you meaning the time when the last change on the media item happened? If so, another user asked about this recently here. If not, could you explain a little better for me what you're looking for?
Răspuns de Sourav Biswas
pe data de 27 iunie 2017 la ora 10:43AM
I was trying to explain a bit different situation here. Say I have an old record(Say 3rd April, 2017) of "https://www.themoviedb.org/movie/10610-the-medallion/changes" movie. Now I want to know if this record is updated since 3rd April, 2017 or not. If yes then depending on change list I want to choose between incremental update or full rebuild of cached data (Primarily Core info, Credits, Images). Or if there is no change, then I can just skip the whole process. Presently to get this yes/no information I have to hit web-service multiple times. Please go through the following example for more clear picture.
Timeline of changes for this specific movie example as of today is
As per present design best approach is to scan for changes from 3rd April to today's date.
Is there any better way? or do you recommend any other design approach to handle this situation more efficiently?
Note: I want to check it adhoc basis, not with a periodic scheduler.
~Sourav
Răspuns de Travis Bell
pe data de 9 iulie 2017 la ora 11:00AM
Given that design, there isn't really a better way right now. The system is designed to be hit in < 14 day windows as that is the max timespan you can get in a single query (14 days).
To meet your design requirement I would implement something like this:
This would return
trueorfalse. Then with that information you could make the decision to walk the change log. It's not a bad idea, and it would be a simple one to add. I could even make it support a key param so you could do this:That covers everything you're asking about, ya?
Răspuns de Sourav Biswas
pe data de 9 iulie 2017 la ora 1:17PM
Yes, it will do the job. Thanks a lot :-)