×
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.
I think I just cut the proverbial Gordian Knot here.
Instead of having this obscenely huge query with the 3-pronged UNION ALL
in the BIRT report definition, accessing a censored view, we put it in
its own VIEW definition (call it SCHEDACTV2), use an uncensored version
of ACCOUNTVIEW, and we add SCHEDACTVIEW.ACCOUNT_ID to its SELECT (so it
can be censored). Then, we create another VIEW definition, SCHEDACTV3,
that applies the censorship function to it.
Then, the query in the BIRT report becomes SELECT * FROM SCHEDACTV3
WHERE USER# = ?
And the result of all this?
A really ugly Visual Explain, when I run it locally in iNav.
And a response time that drops from 20+ minutes to under 8 seconds, when
I put it on the customer box, and run the BIRT report.
--
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
