TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>Opinions, please. Here are two versions of a standard that tells users
>when they should use a particular command:
>1. Use the PREPARE statement for SQL statements that an application uses
>_many_ times.
>2. Use the PREPARE statement for SQL statements that an application uses
>_more than about 10_ times.
>The problem seems to be that what constitutes "many" is in the eyes of
>the beholder. It's arbitrary, depending on many undefinable variables. Too
>much use of a statement by an application results in degradation of the
>performance of the application, but depending on what statement is being
>used and the amount of data being returned, what might be "many" in one
>situation could be "hardly any" in another. I don't think "more than
>about" a finite number helps much. What to do?
How about just "approximately"?
X. Use the PREPARE statement for SQL statements that an application uses
_approximately_ 10 times.
