Yip Ng wrote:
From what the problem description states, it seems so. The symptoms of
this jira
matches those of DERBY-1652. I'll leave it up to the reporter to decide
if it is a
duplicate.
As far as I understand, DERBY-1652 makes this fail also when only a
single trigger is defined. So far, I am not convinced that this
behavior is according to the standard. That is, that a trigger updating
the record it is fired on should result in recursion.
As a data point, this particular problem was raised by customers that
have integrated their product with several DBMSs, and they claimed that
this was only a problem with Derby.
--
Øystein
