Expressing SQL in Design Doc

Subject: Expressing SQL in Design Doc
From: jsokohl -at- mac -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 20 Oct 2004 12:07:10 -0600

Hi all,

I'm editing some info. Developer gives me description of a PL/SQL
procedure, but he capitalizes all the SQL items in the description of the
flow. I think only the SQL verbs should be capped, but he's got'em all
capped--nouns & verbs.

Example (truncated for proprietary code):
Create the Batch Employee Program Reference List.
The ROWSET will contain one ROW for each distinct Batch Employee Program
Name and Description from the Batch Employee Table for the group. Each
WHERE clause receives its own....Ensure that each SELECT statement ends in

I'm mostly interested in the ROW and ROWSET. My convention and my
understanding of the appropriate approach would be to capitalize only
words such as WHERE and GET and SELECT, but not words such as row and
rowset and column and so on.





ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed!

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Follow Up Samples
Next by Author: Re: Expressing SQL in Design Doc
Previous by Thread: RE: Subject: Virtual Machines for training
Next by Thread: Re: Expressing SQL in Design Doc

What this post helpful? Share it with friends and colleagues:

Sponsored Ads