RE: Mixed Case Fields and SQL

i was using iNav for generating the DDL..until i found F.R.O.G.
http://www.innovativesys.net/index.php?pagename=frog&content=frog i
really like how it handles the SQL, etc. all-in-all a nice lil tool...

Thanks,
Tommy Holden



"JK" <johnking@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/21/2007 02:42 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Mixed Case Fields and SQL






Rob,

Thanks for the reply!

1) iNav's 'Generate SQL' function does a great job transferring the
existing
column headings from DDS to DDL - my compliments to who ever wrote it.

2) DDS's ALIAS seems to suffer from the same limitations - upper-case
only.

JK

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, December 21, 2007 2:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Mixed Case Fields and SQL

See also "LABEL ON...". that would change your column headings to mixed
case. Not exactly what you want but helpful none the less.

If you want both names, and still use DDS, see ALIAS.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


"JK" <johnking@xxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/21/2007 03:09 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<MIDRANGE-L@xxxxxxxxxxxx>
cc

Subject
Mixed Case Fields and SQL

The DB analysts at our new parent company are dissing our legacy system
because of the short field and file names. In their world-view, anything
that lacks long, mixed-case column and table names is unworthy of
consideration. I thought I'd take a que from the "Modernization" redbook
and
use this holiday slack-time to redefine the major PFs and LFs as SQL
tables
and add constraints so our DB can be imported into their analysis tools.
The
caveats about multi-member files and record format ids are understood.

SQL examples from textbooks, websites and even the redbook typically

show

mixed-case column names like CustomerId and CustomerName so I'm assuming
that this style is in general usage. Yet, when I CREATE TABLE using
RUNSQLSTM or iNav, the resulting column names are converted to

upper-case

unless the name is wrapped in dbl-quotes. At that point, though, the
dbl-quotes almost seem to become a part of the column name itself, as it
becomes necessary to include the dbl-quotes in the column name whenever

it

is referenced. I can just hear them complaining about dbl-quotes, too!

If the ultimate goal is to have an easy-to-read DB definition, then
CustomerId and CustomerName are certainly easier on the eyes than
CUSTOMERNAME and CUSTOMERNUMBER. I suppose judicious use of the

underscore

character would work, but would definitely be a 2nd choice.

Would someone who has been here before be kind enough to tell me how

the

rest of the world handles this?

Many thanks, JK