Sql Prepared Statements Cleaning

This is a topic to clean up the SqlPreparedStatements topic by describing both sides of the argument without the personal insults. It may be renamed when cleaning is completed and consensus reached.

Top, stop polluting wiki.

WardsWiki mission is to be much more a good resource for the reader, than to be a intellectual sex toy in support for Top's MentalMasturbation. In other words, if some novice software engineer wants to read about a topic like SqlPreparedStatements, he should be entitled to view the current best practices, rather than a horrendous ThreadMess whose only purpose it to make Top feel good about his own level of ignorance.

You've been accommodated with ThreadMess, ignorance and trolling, and what have you, but now you are asking more than what you're entitled to. be happy that you have a TopOnPreparedStatements and all kinds of TopOnXxx? kind of pages, and those pages are referred. If whatever fans you have left out there find your ThreadMess and trolling convincing, they'll still have easy access. -- CostinCozianu

CleanDontDelete? - I agree that threadmess is not pleasant. But let's rework the arguments instead of KILLING IDEAS. That is why this topic is here.

Nonsense. Work your ThreadMess all you want on TopOnPreparedStatements, nobody killed any of your ideas.

I don't like that title. If you can show a majority vote, I will live with it though. Otherwise, what is wrong with say "PreparedStatementDiscussion?"?

Why, are you afraid of your own brand, TOP? The thing is you're arguing alone against everybody (and against best practices) and arguing from ignorance, cause you just don't know stuff. Anything you need to know and you're ShiftingTheBurdenOfProof about it, is easily reachable should you bother to find out.

A "majority vote"? Wasn't enough for you that nobody gave any weight to your argumentation?

How about if nobody contributes to this page from here onward and you'd be left talking to yourself? After all, it's nobody's responsibility to help you out from the corner you out yourself into by arguing from ignorance. And you can exit easily: just go and read about it.

Options Being Compared

1. Embedded String-Based Validators

[to be inserted]

2. SQL Prepared Statements

[to be inserted]

Scenario

A complex query may have several clauses. Under solution 1 each clause can be appended using self-rolled API's such as:

  clauseB = clauseB . ' title= ' . sqlString(workingTitle);

(dot means string append. Some langs can use ".=" to simplify syntax.)

[in progress]