Re: Interupting an rpg sql search -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Interupting an rpg sql search
From: Adam Glauser <adamglauser@xxxxxxxxxxxx>
Date: Fri, 18 Jan 2008 13:47:56 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <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>

Scott Klement wrote:

The only other possibility I can think of is signals.

That crossed my mind too. Tim, if you want to look in to this you might want to by looking at the alarm() Unix-type API. This post http://archive.midrange.com/rpg400-l/200702/msg00258.html might also be of use.

One problem I can think of with the signals approach is that if the timeout occurs, you will end up having to redo part of the SQL processing AFAIK. I kind of like the idea though - if the query takes more than x seconds, pop up a window saying "it seems this query will take a while, would you like me to email it to you, or would you like to start over with different parameters?"

This mailing list archive is Copyright 1997-2026 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.