Post History

I believe one of the main strengths of Q&A websites is that they provide a more digestible alternative to dense documentation. 
Especially for programmers who do not yet know how to find/use the documentation for the language that they are working with.
The answer (and even the question [^1]) is/are not very digestible and therefore they might not be that useful for people looking for an answer to this question.

I don't think vote farming would be an issue, since most people will have a preference and only upvote one or maybe two answers that they would also have thought of (some of the options are just not practically relevant anymore and will probably not be upvoted).

The warning on the top of the answer seems completely misplaced in the context of this question[^1].
They are relevant, but I believe that most people who would need an answer to this question would not understand most of what is stated there.
At least, I would hope that people who are unable to build strings in Python will not be writing critical database code.
Moreover, the warning seems to suggest that string concatenation is a good way to build SQL query strings, which is definitely not the case.
Therefore, I would just drop the warning and/or reformulate the question to provide the context that you want this question to be about.

As a result, I would propose to do **something else**:
Split up the answer in five separate answers and drop the overall warning (and remove the noisy bits[^1] from the question).

[^1]: see the meta comment thread on the question