|
>Hi Peter, >Yes, they are only available through the SQL interface and, as such are >read only (ie. you can't currently use them in RPGLE programs). I don't >know enough about them to know what it takes to be able to perhaps include >them in programs (eg. for insert or update or read) but they make a massive >difference when using query/400. Very quick. The query optimizer >automatically finds the relevant logical (EVI) to use. >Ragards >John Finney " (ie. you can't currently use them in RPGLE programs)" More exactly, you can't use them(never will) in any program. They, Like regular SQL indexes really aren't specified in any program. The Optimizer uses them in determining how to access the table. It can use EVI's in conjunction with regular indexes and with bit maps (as previously noted) via XOR & ANDs . It does keep track of how many destinct occurances exist for the specified key, where the first occurance is and where the last occurance is. Among other things. It is not however a " Everywhere, Everytime, for Everybody " type of thing. They should be used where there is a relatively small number of distinct values for example. John Carr \ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.