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


  1.  Home
  2. RPG400-L
  3. February 2013

Re: More, Re: Questions about RPG service program as an SQL UDF

I suspect that, just as it is when using a function in a WHERE clause, that this often causes a full table scan, esp. when it is something like

function(column) = value

HTH
Vern

On 2/27/2013 6:58 PM, James H. H. Lampert wrote:
I've encountered some further weirdness with my "censorship" UDF.

It seems that last night, I tried benchmarking it: without censorship, a
STRSQL session takes 34 seconds to do a count() on the VIEW. With
censorship, that same count() takes 45 seconds, whether the censorship
is actually suppressing records or not. (Total of over 240 thousand
records in the file.)

On the other hand the BIRT report comes up in a few seconds on an
uncensored VIEW, but sits there for at least 15 minutes, using massive
amounts of CPU, before it coughs up the report from a censored VIEW.

Any idea why there would be such a difference, just from inserting a
WHERE clause that calls the censorship UDF?

--
JHHL


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.