×
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.
Hi Charles,
In my experience, most of the stored procedures written in RPG are
actually set up as "CONTAINS SQL". That's because they tend to be older
code that's being preserved, and called from other languages (such as
Java or PHP) via the stored procedure interface.
Since they're older RPG programs, they don't use SQL themselves, except
for the retrofitted "SET RESULT SETS" that someone added. Since SET
RESULT SETS requires the "contains sql" level, that's what they're coded
with...
Obviously, YMMV.
On 7/19/2010 1:36 PM, Charles Wilt wrote:
Craig,
I guess that 99% of stored procedures are either READS SQL DATA or
MODIFIES SQL DATA.
However, there always that 1%.
Plus, it's not uncommon for user defined functions to be NO SQL or CONTAINS SQL.
HTH,
Charles
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.
midrange.com
