ight have
        propagated data to other places based on the intended update.
        Now an error is thrown to prevent the inconsistent results from being
        committed.  If this change affects your application, the best solution
        is usually to move the data-propagation actions to
        an <TT
CLASS="LITERAL"
>AFTER</TT
> trigger.
       </P
><P
>        This error will also be thrown if a query invokes a volatile function
        that modifies rows that are later modified by the query itsel