×
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.
Alan,
You should NOT do a "SELECT * ..." if you want better performance.
You can do this "existence" checking like this:
EXISTS ( SELECT 1 FROM EMPLOYEE WHERE SALARY > 60000
FETCH FIRST 1 ROWS ONLY )
I learned this trick from this article:
https://www.seg.de/2012-10-existence-check-sql-through-the-ages/ ;
Even though it is not specific to Db2i, it is for "Db2" ... interesting to learn how improving the performance of such "existence" checks has improved over the years.
Hope that helps ...
Mark S. Waterbury
On Tuesday, November 22, 2022 at 03:50:24 PM EST, Alan Cassidy <cfuture@xxxxxxxxxxx> wrote:
SQL references gives an example of EXISTS:
EXISTS (SELECT *
FROM EMPLOYEE WHERE SALARY > 60000)
I would assume that the search in file EMPLOYEE stops when it finds the
first instance of a row that matches.
Is that so?
I'm asking because I'm modifying a program that has a /very/ /heavy/
performance burden, and I have to squeeze milliseconds out of it
anywhere I can get it.
--Alan Cassidy
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
