Note that likely one would want to use the following CREATE INDEX instead:

CREATE INDEX lib.BIGREVENU2 ON lib.ITEM_FACT (SUPPKEY ASC,
decimal(QUANTITY * EXTENDEDPRICE, 15, 2) as QuanXtnd ASC)
/* WHERE decimal(QUANTITY * EXTENDEDPRICE, 15, 2) > 100000 */
RCDFMT BSUPPREV ADD QUANTITY, EXTENDEDPRICE, REVENUE...

Thus the expression is cast to a known type of desirable scale and precision [typically to match attributes of a keyed field for another TABLE; in this case more likely for what is best as input to a HLL pgm], plus the expression gets a specific versus _generated_ column name. The selection could be eliminated, as comment removes in the above, to make the index potentially valuable outside of those queries with that more limited selection.

Regards, Chuck

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].