Mario,

Sorry for the delay in getting back to you.  I profiled the query that
you're using with the latest function version, and that's about as fast as
it's going to get.  With a sensitive result set, the largest amount of time
is actually being spent dealing with the un-optimized WHERE condition in the
source query:

WHERE activo = 'S'

If you remove that, the result is always instantaneous since the function
references will be evaluated as the rows are navigated in the result set.

Even with an insensitive result set, the time it takes to dump out all rows
from the source table is about the same as it is *with* the WHERE condition.

IOW, the majority of the time taken isn't in the function anymore, it's in
the outer query.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Thank you for taking the time to evaluate and profile the function.

Regards,
Mario

"Tim Young [Elevate Software]" wrote:

Mario,

Sorry for the delay in getting back to you.  I profiled the query that
you're using with the latest function version, and that's about as fast as
it's going to get.  With a sensitive result set, the largest amount of time
is actually being spent dealing with the un-optimized WHERE condition in the
source query:

WHERE activo = 'S'

If you remove that, the result is always instantaneous since the function
references will be evaluated as the rows are navigated in the result set.

Even with an insensitive result set, the time it takes to dump out all rows
from the source table is about the same as it is *with* the WHERE condition.

IOW, the majority of the time taken isn't in the function anymore, it's in
the outer query.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com