Re: Retrieving 1, and only 1, row in SQL

[rob@xxxxxxxxx]

Normally I would agree to running the debugger.  But my question is this:
If I do see a performance suggestion, won't it be something like 'create an
index-CPI432F'?  And I am not going to do that on a IBM supplied file.
But I ran the debugger.

select dbname
from qsys2/syscolumns
where dbname='DATDIVF'
fetch first 1 row only
Time=2 sec - not bad
CPI432C - QSYS/QADBILLB  0
CPI432F - DBIREL, DBILB2, DBIATR

select count(*) from qsys2/syscolumns
where dbname='DATDIVF'
 and TBNAME between 'AAAAAAAAAA' and 'ZZZZZZZZZZ'
 and NAME between  'AAAAAAAAAA' and 'ZZZZZZZZZZ'
Time=55 sec
CPI432C - QSYS/QADBILLB  0
CPI432F - DBIREL, DBILB2, DBIATR, DBILFI, DBILFL

I'll probably either bust this down into 2 sql's or 1 api call and 1 sql.

Now for the weird part.  I ran several consecutive time trials.  I would
signoff, signon, strdbg, strsql, and run the above statement.  After a
couple of runs it got to be pretty fast.  Does it store a temporary access
path that it uses, and does this path actually span jobs?


Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin