RE: Re: Export just certain rows?
John Dorlon <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <4120B436C765EC43A31CC3E2A13D36A6225BFE27@ALVMBXW02.prod.quest.corp> |
Right. I just wanted to make sure people understand that even if they decrease this setting they will still have to multiselect the desired rows to export, and then choose to export only selected rows. From: [email protected] [mailto:[email protected]] On Behalf Of Matt Wilkins Sent: Thursday, January 26, 2012 10:14 AM To: [email protected] Subject: RE: [toad] Re: Export just certain rows? I knew that! What I meant was, set it so low that the first fetch has the number of rows you want without having to scroll. Then just work with those rows. However, I can't get it to return fewer than 60 at a time. From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of John Dorlon Sent: Thursday, January 26, 2012 11:01 AM To: [email protected]<mailto:[email protected]> Subject: RE: [toad] Re: Export just certain rows? That won't limit the number of rows returned, it will just decrease the number of rows returned per fetch. From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Matt Wilkins Sent: Thursday, January 26, 2012 9:59 AM To: [email protected]<mailto:[email protected]> Subject: RE: [toad] Re: Export just certain rows? But you can limit the number of returned rows by setting the OCI buffer array size as well...as long as you're using F9 (run as statement). From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Zarzycki, Michael Sent: Thursday, January 26, 2012 10:25 AM To: [email protected]<mailto:[email protected]> Subject: RE: [toad] Re: Export just certain rows? Yes, the silliness is rampant. Can I assume the answer to the OP's original question is that TOAD has no utility for extracting a portion of a result set after the query has been run? You can only control that by limiting the return in your SQL. The only kluge I can come up with is you let the query spool its initial 500 rows, start the extract, then cancel it. You will get more than 50 rows, but much fewer than the total result. Best regards, Mike Michael S. Zarzycki, MTS | IT Engineering, Integrations, and Programming Manager | Sensata Technologies, Inc. | voice: 508-236-1015 | fax: 508-236-3701 | www.sensata.com<http://www.sensata.com> | The World Depends on Sensors and Controls -----Original Message----- From: [email protected]<mailto:toad%40yahoogroups.com> [mailto:[email protected]<mailto:toad%40yahoogroups.com>] On Behalf Of Norman Dunbar Sent: Thursday, January 26, 2012 10:10 AM To: [email protected]<mailto:toad%40yahoogroups.com> Subject: Re: [toad] Re: Export just certain rows? On 26/01/12 14:58, Bert Scalzo wrote: > Well since we're being silly J > > Where rownum in > (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50) In which case, I can go even sillier and lees effient as well: where mod(rownum) in (1,2, ..... 51) Might as well read the whole table eh? ;-) -- Cheers, Norm. [TeamT] ------------------------------------ Yahoo! Groups Links