Yoda

Yeah, I was never really taught much about databases but in my previous job where I worked three years this one guy was a master at all that sort of stuff. He taught me how to build simple commands in C# to utilise large-scale databases that we managed. Stuff like inserts, querying, and then joins too. I never got that good at it and wouldn't know best practices but I got to a competent level.

It's mad to think how many skills you must have learned as a result of starting up this movie forum all these years ago

Oh cool, yeah I get you! That makes a lot more sense to have a table of entries and then just grab the data when needed to get the final top 100 or ranked table. Sounds like the process for the host then is a lot more straightforward now - not trying to take away from the task - but more a question of thread presentation, sorting out posts etc.

Ah cool, I don't know how much interest I have in war films personally but I'll keep an eye on what the forum decides next and have a think anyway

Potentially in the future! Although we're running out of lists to do

Looking back through the 60s thread and I'm loving the graphics I made, even a GIF for the header image... I must have had loads of time on my hands back then.

I love the additions you've brought in, the differentiated post types for the actual film reveals and even the list submission form. I'm guessing in the future you could get that so the post submission as well as just sending a PM to the host and sender, you could fire off to an online database like MySQL where you'd have three columns, a film ID from themoviedb, points which we add to each time and lists which we increment by 1?

I haven't worked in PHP in ages and use C# nowadays but could potentially give a hand with that as the process will be the same so will just come down to syntax. Like I said though we've worked our way through most of these lists anyway... are the any ideas what the next one could be?

That’s a good one, too, but I meant the one lets you can specific the width: img_size