Well, Peter said the trigger was "like" the one he showed, so the
actual one may be more complex. In any case, if these bugs are
relevant, there should be an OutOfMemoryException in the log. If not,
they are not relevant.
Daniel John Debrunner wrote:
Michelle Caisse wrote:
See http://issues.apache.org/jira/browse/DERBY-443 and
http://issues.apache.org/jira/browse/DERBY-759. There is an issue
handling OutOfMemoryExceptions that can result in this error.
Not sure I see the connection with those bugs. I don't see how this
trigger would lead to an out of memory situation. Or is it because there
is a BLOB/CLOB in the base table of the trigger?