× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. February 2016

Re: SQL Naming Conventions

Very good advice to assign long SQL names. Your data should be consumable
by query users outside IT/IS, and your data will be a lot more meaningful
to them using long names.

IMO, for new development, use of the long names should be enforced by
standards / code review. Developers should have efficient tools to fetch a
the list of columns from a table, so they can copy/paste them instead of
keying them.

Mike



date: Fri, 26 Feb 2016 14:22:24 -0500
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: SQL Naming Conventions

Get a copy of this book, Joe Celko's "SQL Programming Style".

Note that for IBM i, current best practice would be to assign a long SQL
name along with a 10 character short name.

Charles



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-2024 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.