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



On Wed, Apr 20, 2016 at 11:53 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Is there any practical reason to know the difference?


I don't think so, but you don't know what you don't know sometimes.


Any source file is not to be trusted and one
should rely upon a 'generate sql' option if you just 'have to' retrieve
the 'source'.


I agree. As a matter of fact, when I'm required to use source members to
store the source, I use qsys2.genetate_sql to do so. I do see merit in
storing the schema in source members, but I''d prefer them on the IFS next
to my application source code so that a build script could create the
tables on a new machine.

Honestly, if you want to convince a hardcore green screener not to store
DDL in source members, a good first step i to convince them to always
populate the source member with qsys2.genetate_sql. That will let them gain
confidence in the IBM stored procedure. Then they will eventually realize
they are "suspenders and belts" and drop their old ways.

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.