This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
To prefix, or not to prefix.  That question comes up alot.

I vote against prefixing in the database itself.

Makes querying the database cross reference files much easier.
select system_table_schema, system_table_name, system_column_name
from qsys2/syscolumns
where system_column_name='LOCATION'
order by 1, 2, 3
SYSTEM_TABLE_SCHEMA  SYSTEM_TABLE_NAME  SYSTEM_COLUMN_NAME
    ADTSLAB             PARTORDER           LOCATION
    ATSDLSSQL           SYSPACKAGE          LOCATION
    DHTBRAF             DUNDST              LOCATION
    DHTDIVF             DUNDST              LOCATION
    DHTIREF             DUNDST              LOCATION
    EDI.GDI             DUNDST              LOCATION

When you are joining multiple files then you don't have to remember
cmcust=clcust

Invariably someone forgets to prefix a field anyway, even in vendor
supplied software.

And, while the drop may be useful for those of us forced into using files
with prefixed fields, those who will use it might not be inclined to
prefix their fields in the first place.

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.