Remove duplicitous Point Prime tracking

[jyundt]

Previously, when a Participant won the point prime the following would occur:

• The participant had point_prime=True set
• A Prime object was added with the name 'Point Prime'

With this change, we are no longer creating the additional Prime object and inserting it into the database. The Race view will add an additional row to the Primes table if a Participant has point_prime=True

[johnwheffner]

I assume when releasing this you'll just run a sql script manually that drops all primes called "point prime"?

[johnwheffner]

Small thing: if somehow there were ever multiple point primes for a race (for instance, if there was a tie?), this would silently show only one, arbitrarily. It might be safer to write the code handling it as a collection and loop over all of them rather than treat it singularly.

[jyundt]

I assume when releasing this you'll just run a sql script manually that drops all primes called "point prime"?

You say "script", I say "run the first sql command that pops up on SO and hope for the best..."

But yes, I'll manually clean up the old Prime entries after this is pushed.

Small thing: if somehow there were ever multiple point primes for a race (for instance, if there was a tie?), this would silently show only one, arbitrarily. It might be safer to write the code handling it as a collection and loop over all of them rather than treat it singularly.

Not a bad idea, it might also help us (visually) see if there are >1 Participants with point_prime by mistake.

[johnwheffner]

You say "script", I say "run the first sql command that pops up on SO and hope for the best..."

Well, you do work at Uber...

[jyundt]

You say "script", I say "run the first sql command that pops up on SO and hope for the best..."

Well, you do work at Uber...

Yikes, I'm going to need some ointment for that burn...ouch.