Um, ew, no... not for this situation. All that would be needed to fix it is a limit on the sql return. It would also help if it didn't duplicate entries or instead, had a count column for the downloads... like I was testing downloading a certain map people were having problems with and downloaded it like 20 times while testing some new code for it, now, I got 20 entries of me downloading that file... which all got listed when I used that portion of the script. I wouldn't recommend a count column for senv5 though, just a simple record once with your latest download date *IF* you feel the need to record downloads. You could make some pretty good functions with such a table... such as a little field in the map view page saying "You downloaded this file on XX-XX-XXXX", so you could possibly avoid downloading the same file twice while browsing for maps... and then you could have a simply functionality option to delete or mark download entries as null to avoid seeing that message if you like reformat or lost your maps and want to know what maps you've downloaded RECENTLY... or... such a table could also tell you if the map was updated since you last downloaded it...
There is so much possibility in a new dldb script in like every area possible, don't screw it up
.
Edit (since you replied to the topic while I was writting):
Beer, no...
The bandwidth apparently came from 2 functions that seemingly loaded the entire file for reading(?) so it can dynamically get the file size (instead of, perhaps, caching it). It also did this for screenshots. Senv4 dldb does almost everything wrong and doesn't care what resources it uses.