I don't know off the top of my head, but if you don't get joy off the list you could experiment with a packet sniffer. You could probably infer the answer to the question by looking at what actually gets transmitted on the network.
tcpdump, snort and ethereal are common packet sniffing tools. Nigel. -----Original Message----- From: Andrew Perepelytsya [mailto:[EMAIL PROTECTED] Sent: Friday, 4 April 2003 10:17 a.m. To: [EMAIL PROTECTED] Subject: again ORDER BY and ROWNO Don't be afraid, it's not another query on 'how' ;) . I am quite familiar with the limitations and workarounds for this issue. I managed to solve this problem the following (Java/JDBC) way, though I would like to hear if I'm missing any points here: 1. we want to select, say, top 10 companies in our query. 2. we write a query and sort the companies by revenue (ORDER BY revenue DESC). 3. the main point ==>> in Statement interface we have a setMaxRows(int max) method. The docs say that the driver simply drops rows if excessive rows are supplied. 4. it seems to work pretty fine at the first glance - at least as the user sees it. Now, what are the internals for this process? Is it a similar approach to writing a DBPROC and FETCH'ing the rows in a loop? What interests me most, is 'are we getting only the rows we want through connection or is it just a dumb cut and the whole table gets physically transmitted under the hood?'. __________________________________________________ Yahoo! Plus For a better Internet experience http://www.yahoo.co.uk/btoffer _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
