useless to the vast majority of cases where
quotes are required.
Huh? Quotes are required in zip-codes?
Phone numbers? Show sizes? Medical doses?
Time? Date? IQ scores? (hint, hint, hint)
I can only think of 1 field (last name) in our apps. Those
we WILL change. (Even though we don't have
any employee that has a quote in their last name.) O'Brian, etc.
a) Use your system, but only if quotes are
never needed, and hope it works.
I've already said (over and over again) quotes
are NOT needed in our applications.
b) Use paramaterised queries, which always
work, all the time, even if quotes are there.
They will not work when it's impossible for us
to hire the people, have the time, the budget,
the resources, etc... to search 100,000s of lines
of very old code.... to fix something that can
be fixed simply by removing quotes.
Instead of telling us to spend $85,000... why
not just post the code that will break... if we
remove all quotes... and don't use parameterized
THAT is the question here. Nothing more.