On Thu, Jun 26, 2008 at 5:08 AM, Dean Rasheed <dean_rasheed@xxxxxxxxxxx> wrote: > The Oracle "instead of" trigger ducks this issue completely. The > trigger is called once per row in the view that matches the top-level > "where" clause, and it is entirely up to the author of the trigger > function to work out what to update (if anything). That sounds like exactly the sort of thing I was envisioning. Although from what Tom said, it sounds as though "instead of" triggers in PostgreSQL would have to be implemented in a significantly different way from other triggers. How does an Oracle "instead of" trigger decide how many rows to tell the caller were updated? Can this "return value" be modified programmatically by the trigger? Mike
