I've been looking at the errors in derby.log of TriggerWhenClauseTest. Some of them seem to be syntactical errors
I think that's probably expected. A lot of the Derby test suites intentionally submit SQL statements with syntax errors in them (in order to test that the syntax errors are properly detected and a reasonable error message is returned). So the derby.log after running a test may be FULL of messages, many of them completely normal. That does make it a challenge if you are trying to distinguish the expected error messages in derby.log from the unexpected ones. bryan
