I observed that the change to miscerrors.sql in revision 558801 are causing test failures in junit suites in some environments, see for example
miscerrors(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)junit.framework.ComparisonFailure: Output at line 69 expected:<...where CAST(SQL_TEXT [AS LONG VARCHAR) LIKE '%932432%' ] ...> but was:<...where CAST(SQL_TEXT [ AS LONG VARCHAR) LIKE '%932432%'] ...>
I think, from reading logs from nightly regression tests and my own tests, that the order of the two output rows from the statement
ij> select SQL_TEXT from syscs_diag.statement_cache where CAST(SQL_TEXT AS LONG VARCHAR) LIKE '%932432%';
varies between JVM versions (e.g. Sun JVM 1.6 has correct order according to the master file, while JVM versions 1.4 and 1.5 have the opposite order), hence causing the failure.
Kathey, was it intentional to include an extra space in the above mentioned statement (between "TEXT" and "AS")?
I think if the second space is removed, the result will contain one row instead of two, and we won't see this diff any longer...