|
Careful. In the case of a select (which I assume you're using since you mention a resultset) the number of rows is a guess and nothing more. CPUs count, query parallelism, and order by clauses should all have an effect on the guess. In an action query (update, delete, etc) the rowcount is accurate, but not in a select. I'd look at count(*) if that fits your needs. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: Hatzenbeler, Tim [mailto:thatzenbeler@clinitech.net] Sent: Tuesday, May 07, 2002 17:48 To: 'midrange-l@midrange.com' Subject: RE: SQL Result Count Question.. This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Thank you... I will check that variable out... > -----Original Message----- > From: Buck Calabro [SMTP:Buck.Calabro@commsoft.net] > Sent: Tuesday, May 07, 2002 2:47 PM > To: midrange-l@midrange.com > Subject: RE: SQL Result Count Question.. > > Tim wondered: > > >My question is this... Do I have to loop > >through all the lines in the result set > >using fetch next, or is the a value I can > >read after the SQL runs that contains the > >number of rows? > > Predefined value SQLER3 (for RPG) provides the number of rows. > > It's in the manual. > http://publib.boulder.ibm.com/pubs/html/as400/infocenter.html > V5R1 > Programming > SQL > SQL Reference (HTML) > Appendix B (SQLCA) > Field descriptions > http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/info/db2/rba > fzms > tf > ielddescsqlca.htm#HDRFIELDDESCSQLCA > > A search for SQLER3 turned up 4 hits, including the above. > > --buck > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or privileged information. Any unauthorized review; use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy the message. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.