|
Bob, I'm not completely convinced this would perform well enough given the number of records you are working with but I'll throw it out as an idea anyway. What about using a user index to order the records? The index portion of each entry can contain the field to sort by which gives flexibility there. Entries can be written or read in large blocks since the API's work with buffers so I/O is minimized. API functionality mimics chain, read, reade file access. There are the API calls though. Just a thought, Rick -----Original Message----- From: Bob cozzi [mailto:cozzi@xxxxxxxxx] Sent: Wednesday, August 13, 2003 9:52 AM To: rpgiv@xxxxxxxxxxxxxxx; 'RPG programming on the AS400 / iSeries' Subject: Subfile "sort" thoughts I have a situation were I need to help implement a subfile sort. There is a Work-with panel that contains about 7 fields, all of which the end-user wants to be able to sort by. Nothing to unusual about this so far. But in this situation the file is actually a dynamic file created with an SQL UNION ALL statement that ends up producing about 9 million records. I was thinking about a page=size subfile and will offer the end user a filtering option to weed out unwanted transactions. What I'm wondering is how to attack the subfile sort in this context; 9 million records+ doesn't lend itself well to any conventional techniques, such as sorting a multiple occurrence data structure or even dynamic/runtime querying via SQL or Open Query File as the performance will suck. So I'm wondering about building an SQL view out of the UNION ALL statement, and then using SQL further (pre-runtime) to create an index over each of the 7 fields. But I'm not sure if this is the right solution. Comments? Suggestions? Bob Cozzi Cozzi Consulting www.rpgiv.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.