Don't allow uploading a previously-uploaded puzzle?

[dpsanders]

Maybe it would be a good idea to not allow a puzzle to be uploaded if it has previously already been uploaded?

[ewmson]

Now that the puzzles have been moved into postgres we should be able to enforce this with a constraint.

I think we want to allow non public (people testing or not wanting to publish) to have duplicates and only apply the constraint on the public one.

If we do go this route, there is a question of the past data as solves will be associated with different puzzle ids, but refer to the exact same puzzle. I suspect we can just start enforcing the constraint going forward to not worry about the past.

[fg123]

In a similar realm, including other types of meta-data would be useful too, such as an "uploaded date" versus the puzzle date (i.e. for dated puzzles like NYT or LA Times). This would allow for retroactive uploading of puzzles but still allow front-end to sort by puzzle date, for example.

[stevenhao]

duplicate of #15 (no pun intended)