taesup
commented
10 years ago Working from your last question back, If the user has more ads than slots, a random but exhaustive selection of ads are chosen until the number of slots are filled. In the opposite scenario, if there are more slots won than there are ads, a random but exhaustive selection of ads are made until all the ads are exhausted, at which point all ads are marked unused and another round of random but exhaustive ad selection begins, this continues until all slots have been filled.
It's trivial to sort ads by location at the time of auction close but I'll have to create a new DB object to hold a snapshot of all ads in rotation at the time of auction close along with the additional information of each add such as price per slot and paid status (which in and of itself will need to be recalled and updated in the future). The winners are still allowed to takes ads in and out of rotation which brings up the question of whether the snapshot will need to be updated at that point as well.
For each ad auction, view all ads grouped by region on a single page. Would be more informative if the account name, price per slot and paid status were also displayed per ad.
It would be additionally helpful if this information were frozen for historical record to be able to see this for all past auctions.
How would it handle rotations where a user has more ads than slots?