Andrew,
Roger on the releases table, however, I'm not sure I totally agree with you on the 'solution' giving me 'freedom'. :) I think caching and maintenance goes without saying, but having efficient queries to begin with would assist both me and the api load. I know I'm preaching to the choir here and that Giantbomb plans on expanding the system, I just wondered how I could pull it off if and if I was missing something. For instance, if I wanted to get 2011 releases in January I can't see a way to do it without reading (and caching) the entire database. Then, if there is an update, I can't sort by latest_updates so I have to read every record to see if there are any updates since the last cache. Seems like a pretty heavy load to pull that off. I think the solution is to just to not do it and patiently wait. :)
Log in to comment