Change History

Take these two checkers:
https://project-gc.com/Challenges//111480
https://project-gc.com/Challenges/GC536C2/111479

In theory, they should do the same thing, with the one using favorite_points_pct directly, and the other calculating favorite_points_pct = floor(favorite_points / num_finds * 100). However, the favorite_points_pct field is considerably higher. For example, running myself on the calculated version, the first entry is:
GC735VZ - 198/352 = 56%

That similar entry using the field is:
GC735VZ 198/352 = 64.2857%

Is the favorite_points_pct field not just supposed to be favs/finds? Why is this field in the DB, since it can just easily be calculated?

Take these two checkers:
https://project-gc.com/Challenges//111480
https://project-gc.com/Challenges/GC536C2/111479

In theory, they should do the same thing, with the one using favorite_points_pct directly, and the other calculating favorite_points_pct = favorite_points / num_finds. floor(favorite_points / num_finds). However, the favorite_points_pct field is considerably higher. For example, running myself on the calculated version, the first entry is:
GC735VZ - 198/352 = 56%

That similar entry using the field is:
GC735VZ 198/352 = 64.2857%

Is the favorite_points_pct field not just supposed to be favs/finds? Why is this field in the DB, since it can just easily be calculated?

Take these two checkers:
https://project-gc.com/Challenges//111480
https://project-gc.com/Challenges/GC536C2/111479

In theory, they should do the same thing, with the one using favorite_points_pct directly, and the other calculating favorite_points_pct = favorite_points / num_finds. However, the favorite_points_pct field is considerably higher. For example, running myself on the calculated version, the first entry is:
GC735VZ - 198/352 = 56%

That similar entry using the field is:
GC735VZ 198/352 = 64.2857%

Is the favorite_points_pct field not just supposed to be favs/finds? Why is this field in the DB, since it can just easily be calculated?