Re: trigger question

DB2/400 Triggers allow the columns in the triggering row or another row to be changed by the Trigger. In article <E4oAB0.BoA@nonexistent.com>, Jacob Salomon <jake@apparel.net> writes: |> |> this is documented (I forget where): In the trigger action (or in a |> procedure that the trigger action calls) you cannot modify a column that |> tickled (OK, invoked) the trigger. This applies even on that column in |> a different row of the table. Grrr! Frustration!! |> |> This was imposed in order to prevent recursively called triggers, which |> could [conceivably] cause a stack overflow. |> |> Editorializing follows: |> |> I really wish they would remove this restriction. If they are worried |> about stack overflow, let them impose a limit on stack depth, as they do Kenton Milligan DB2/400 Development IBM Rochester-AS/400 Division kmill@vnet.ibm.com GO HAWKEYES!! (opinions stated are not necessarily those of my employer)