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



I think all of us were given as our first commandment:
"Thou Shalt Not Name any Object Beginning with "Q".

and now looking through QSYS2, I would extend that commandment to
.... and also "SYS"

I will put in a RDC...



On 2/9/2015 2:27 PM, rob@xxxxxxxxx wrote:
I will grant you that there is quite a difference between 'system name'
and 'SQL name'. When it comes to SQL name, IBM tries to follow the norm.
If you've ever seen SQL Server or any number of other SQL packages you
will see a similar "system catalog" with things in there like SYSCOLUMNS
and SYSTABLES. Are you suggesting that all future catalog additions have
obfuscated system object names that begin with Q? While their 'SQL name'
be meaningful? I suppose you could suggest that with a 'Request for
Design Change' or a COMMON Requirement.

What is really a hoot is when they create SQL built in functions that
match existing column names. For example, when they created RID for row
id. Which happened to be the name of an existing column in Infor's FRT
table (record id, think old active record code). This didn't cause any
existing embedded SQL to collapse but if you went to recompile that
program you had to start enclosing the column name with double quotes
("RID") if you wanted the active record code versus the reserved word, row
id. I'm willing to bet there's no way IBM would obfuscate the BIF, (nor
would I want them to).


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.