Re: 428EC on current_date in MQT

from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: 428EC on current_date in MQT

Makes sense to me...

The idea behind a MQT is that the DB would be able to redirect a query to
the MQT automatically

For example, you find your users running a lots of a query like so
select division, sum(sales) as totSales
from myTable;

So you create an MQT...

Now whenever the users run the above query, the Db would use the MQT.

One can also query the MQT directly, but the point is your users don't have
to know about it or make changes to what they are doing.

Thus it makes sense to me that the DB doesn't allow the use of special
registers or global variables which could change in the MQT select
statement.

Honestly, I've found very little use for MQTs since Db2 for IBM i doesn't
support system maintained ones.
Everything I've considered them for was better served by a EVI with
calculated fields as those are maintained by the system.

HTH,
Charles