RE: w/%editc() - Qualified Names

[rob@xxxxxxxxx]

Hear!  Hear!

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Bob Cozzi
                    \(RPGIV\)"              To:     <rpg400-l@midrange.com>
                    <cozzi@rpgiv.com>       cc:
                    Sent by:                Fax to:
                    rpg400-l-admin@mi       Subject:     RE: w/%editc() - 
Qualified Names
                    drange.com


                    02/28/2002 11:01
                    AM
                    Please respond to
                    rpg400-l






John,

What's the difference between specifying a field named  XXNAME in SQL
and using a co-relational name xx.name?

I think if they want to query the customer master file, they would
perfer to specify CITY, STATE, ZIP rather than CSTCTY, CSTSTE, CSTZIP.
Besides, do end-users do JOIN functions when they run Query/400? If
they're that smart, they can handle read field name.

Bob Cozzi
cozzi@rpgiv.com
Visit the on-line  Midrange  Developer  forum at: http://www.rpgiv.com


> -----Original Message-----
> From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]
On
> Behalf Of jpcarr@tredegar.com
> Sent: Thursday, February 28, 2002 9:38 AM
> To: rpg400-l@midrange.com
> Subject: RE: w/%editc() - Qualified Names
>
>
> >The PREFIX keyword now allows you to use real field names in your
> >database, and if you like, assign a prefix to those field names at
> >compile time. It's pretty cool.
> >
> >Bob Cozzi
>
>
> I like the Prefix too.   Especially with the same file in the PGM more
than
> once.
>
> However,  The Prefix, while neat for Programmers,  still leaves End
Users
> who use (say) Query/400 to have to qualify names,  and forces the use
of
> correlated names in SQL.
>
> While you can do that in both places,  It's a tedious effort that is
not
> required if the DB is named that way.
>
> I look at it from this view.
>
> Customer# has one root definition,
> All files that Contain Customer# inherit the properties of the one
> definition(Class).   I like each "Instance" of Customer# to be
inherently
> qualified by the name of that Instance to specify which SubClass that
> instance belongs to.
>
> Root Definition
>
> Cust
>
> Customer Number in file XXPFZZZ
> Will have the "Qualified Instance" Name of ZZZCUST
>
> Customer Number in file XXPFAAA
> Will have the "Qualified Instance" Name of AAACUST
>
> WHERE EVER I see ZZZCUST or AAACUST I know which instance I am talking
> about.
> AND  it does NOT vary from program to program, display file to display
> file.
>
> Prefix names are/can be different in each program. Without an External
> definition
> forced upon it.
>
> Where XX is the System name (like OE for order entry, PP for
Production
> Planning, etc)
> PF is a part of the Object Naming meaning Physical File (DF, CL, RP,
LF,
> etc)
>
> Just opinions folks.  However I never worry about field name
collision. And
> I have a system wide naming consistency.  Whether in RPG programs or
> Query/400's or talking to end users using a graphical query tool.
>
> The qualified Instance Name is the Qualified Instance Name.
>
> What ever works for you.
>
> John Carr
>
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.