NOTE: The following pertains to the Survivor (side) pool only. We do not use standard weekly pool.
So after much testing / trial and error, we are bailing on the statistics page. As for standings, we are just going to manually export from database and post pdf around 1:30 ish on Sundays. Not ideal, but we are not taking any chances this year. Last year was a mess to say the least; here are problems and solutions that might help you until we can develop a query for survivor standings page to support a large user base (Our count now is at 297, projected to break 300 users before kickoff!!!!):
Problem:
- Users not able to make picks when large number of users are trying to pick at the same time
Solution:
- MS SQL of course!!! Thanks to mrpolaris, todhend, and everyone on this thread, we are now running the MS SQL version.
Problem:
- Standings page does not load due to size of user base and number of queries
Solution:
We encountered a problem after users make pick. The standard entry page redirects users to the "standings" page once user submits pick. This is bad news for our pool, as the standings page does not work 99% of the time.
As a work around, we created a "confirmation" page for users to go to instead of the standings page. This page is just a static page that tells user he or she has successfully submitted pick.
- User clicks "entry form"
- User makes pick and clicks "update"
- Pick is logged in database, then user is directed to static confirmation page stating pick was successful
Our next goal is to make a page where user can click and view their current pick for the week. I wrote working script to output username, current week, but need help pulling the actual pick from the data base table for the current week to display. Yes, I am a .net newbie, so please do not laugh.
Problem:
Since standings page does not load, no one knows anyone's picks after kickoff
Solution:
Very unrefined, but it works. After all picks are locked, we load up database in MS SQL Server Management Studio (free program). Once in, we export all rows from the table "SidePicks" in CSV format. Using OpenOffice.org software, we sort data and include title, etc. Once data is good to go, we export to pdf file. In place of the standings page, we created a new page to where we post pdf of all picks. Each week, we will continue posting pdf's, so all weeks will be included with downloadable links in an unordered list.
Now if we can get a working standings page, the pdf method will not be needed. This is where I am stumped, especially given we have around 300 users. The current standings query is simply too large to work with this many users. I am thinking if we could create a smaller query, maybe to just pull for the current week instead of every single week, we may be able to have something the works.
Sorry to let you down progressive, hopefully these ghetto fabulous solutions work in the meantime!