×
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.
On 2/27/13 5:57 PM, Vernon Hamberg wrote:
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
The bizarre and unexplained issue is that the censorship function adds
only a modest 11 seconds to the response time when I benchmark it by
counting the rows in the view (which would have to call the censorship
function for every single record), yet it adds at least 15 minutes to
the response time when a BIRT report is run. Yet when I added diagnostic
code, to log the initialization of the censorship function and each
record passed to it, running the BIRT report logged exactly one trip
through the entire file, and four additional calls to specific records.
And (based on my recollections of a class I took in Rochester back in
2005) I was under the impression that Visual Explain required one to run
the query through iNav, or something connected to iNav. How would that
help me with BIRT?
--
JHHL
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.
midrange.com
