Answer question as asked or answer with recommend redesign [duplicate]

Question

Possible Duplicate:
Is “Don't do it” a valid answer?

If the underlying implementation within a question may deserve redesign (depending on OP's intent), should the answer address the question as it is stated, or assume the redesigned is warranted and answer the question under the redesigned principle?

A question is asked specifically about a given topic. The design used in the question is arguably not the best design for 70%-80% of uses, but is sometimes perfectly legitimate. And the design is directly related to the topic of the question.

It boils down to: Which one of these responses is most appropriate (and which are inappropriate)

1. Answer the question as is
2. Comment on the question with recommended design, then answer question as is
3. Answer the question with recommended design
4. Comment on the question with recommended design, then answer the question with recommended design
5. Other?

The specific situation I found myself is here - but I assume this incident isn't isolated.

Answer 1

I answer the question that is asked, but point out that there is a better way to do it, explain why, and give an example. Like this:

---

Use the UPDATE statement:

UPDATE STUDENTS SET NAME = '" + Name + "'";

However, you shouldn't do it this way, as it leaves you vulnerable to SQL Injection. Consider using parameters instead, like so:

UPDATE STUDENTS SET NAME = @Name;

Answer 2

The problem as I see it is that often a coder who is having difficulty solving a problem will ask a specific question on SO regarding a code solution that they are trying to use to solve the problem, when the real issue is that they're barking up the wrong tree, that there avenue of approach is wrong to some degree or another.

In my admittedly biased opinion (and that's all that this question can be about), the best solution is to get as much information about the problem domain from the original poster, and then based on that (or failing that, try to make the best assumptions about the problem domain ) post the best solution for the problem domain rather than automatically solve the direct question. If a solution is offered that just solves the concrete question, there should in the very least be some discussion on whether there may be better approaches to solving the problem at hand.

Edit: You State:

The problem domain can still be unclear.

I agree 100% and that is why part of our responsibility is to try to clarify it as much as possible before answering, or given continued ambiguity, answer as best we can with caveats.

Also, if we only answer according to the OP's interpreted intentions, doesn't that imply that the only benefactor of the question is the original poster? By the time someone else sees the post, the context of the question could have changed (OP's reputation in our case).

I think that just the opposite is true. If we answer the OP's specific question, we are just doing that, solving a specific code issue while possibly ignoring the greater problem -- that of what is the best way to get keyboard input in this situation. By answering the overall problem, we increase the odds of helping more folks with similar problems in the future. We don't want to be too narrow in our answers as to not see the forest for the trees.