Hi Bryan, I wrote a new test that has more than one trigger clause and when clause. The trigger fails to update like the previous test when I run the new test in a clean sandbox, but when I run it with my last patch I get an error
ERROR XCL12: An attempt was made to put a data value of type 'java.lang.String' into a data value of type 'INTEGER'. I'm still working to know why this is happening. The trigger is successfully created, so I infer that the bug is not because of the changes I made in the last patch, this error comes up when the trigger action takes place. I haven't made changes to that part. On Tue, Jun 9, 2015 at 5:39 AM, Bryan Pendleton <[email protected]> wrote: > 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 > >
