Re: Is there a workaround for the 'mutating table' problem in a trigger ?

Get a database with a more complete trigger solution...

In article <4kunnm$9u8_at_dfw-ixnews6.ix.netcom.com>, vinayak_at_ix.netcom.com(Vinayak Kulkarni ) writes:
|> In <31726A87.353D_at_theta.co.nz> Rob Benson <robben_at_theta.co.nz> writes:
|> >
|> >coolcat_at_citynet.net wrote:
|> >>
|> >> Hi
|> >>
|> >> In a trigger on a table, I want to do a
|> >> SELECT MAX() ...
|> >> from that table and update a denormalized column in another table.
|> >> .....
|> >> TIA.
|> >
|> >In earlier releases (7.1.3 back I think) you could get around this
|> >by selecting from a view based on the table concerned BUT I notice
|> >in 7.1.6 that this no longer works. Will get back to you if I
|> >think of a work around.
|> >
|> >--
|> >**************************
|> >Rob Benson
|> >Theta Systems Limited
|> >robben_at_theta.co.nz
|> >http://theta.co.nz/theta
|> >
|>
|> TWO SOLUTIONS :
|>
 

-- 
Kenton Milligan
DB2/400 Development 
(opinions stated are not necessarily those of my employer)