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

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.