“…We avoid materialization because (a) it would require a sophisticated middleware database that can support incremental view updates and triggers over nested views, and (b) it would require the view to be updated for every relevant relational update even though user triggers may have very selective predicates. 1 In contrast, most incremental view maintenance algorithms (e.g., Abiteboul et al [1998], Bohannon et al [2004], Ceri and Widom [1991], Dimitrova et al [2003], El-Sayed et al [2002], Gluche et al [1997], Kawaguchi et al [1997], Kuno and Rundensteiner [1998], and Rys et al [1996]) assume that the view is materialized, and use the materialized old value of a row to compute its new value. We thus need to devise techniques that can selectively compute the relevant new values directly from the base data.…”