|
Hi John, > It was simply due to the ability to fetch > by offset. I was thinking about a PF in QTEMP > with record lengths of 32767. > My only other alternative was multiple user > spaces and just limit the retrieval to 160 meg > or so. > John You wouldn't have to limit the results if you were only "streaming" the data to the application. Data could so eg. pass the line, your program, the users SQLRPGLE program (or?) and then end up on paper. Or been written to disk by the user program, in total or by selection. But the sentence "fetch" implies in me that you are willing to cache the whole thing to be able to wade thru it by means of a cursor. What jumps to mind is what happens when someone creates a cursor and positions it to the end of the file? Would that be a problem/major performance hit? :-) -- Mit freundlichen Grüssen / best regards Anton Gombkötö Organisation und Projektleitung Avenum Technologie GmbH Wien - Salzburg - Stuttgart http://www.avenum.com
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.