Re: Close SQL Cursor without Ending Module -- RPG400-L

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

Subject: Re: Close SQL Cursor without Ending Module
From: Dave <dfx1@xxxxxxxxxxxxxx>
Date: Wed, 5 Dec 2012 20:22:43 +0100
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

2012/12/5 CRPence <CRPbottle@xxxxxxxxx>

On 05 Dec 2012 11:51, Charles Wilt wrote:

One must keep in mind that the DELETE FROM TABLE_NAME honors override
to database file [OVRDBF] that are scoped to the procedure performing
that SQL DML request, but the CLRPFM does not. That impact can end up
being a nice feature or a horrible flaw, depending on how\what is
replaced by the noted CLRPFMSQL request; so... just a word of caution.

Wow, who knows how many programmers jobs Chuck just saved!

As an Amazon Associate we earn from qualifying purchases.

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.