db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: test failures when built & run on linux...(from thread re derby 13)
Date Wed, 12 Jan 2005 19:41:12 GMT
Hash: SHA1

Shreyas Kaushik wrote:

> Sure, here are the tests that failed,
> derbylang/derbylang.fail:lang/desc_index.sql
> derbylang/derbylang.fail:lang/distinctElimination.sql
> derbylang/derbylang.fail:lang/inbetween.sql
> derbylang/derbylang.fail:lang/predicatesIntoViews.sql
> derbylang/derbylang.fail:lang/subqueryFlattening.sql
> derbylang/derbylang.fail:lang/triggerGeneral.sql

I have an idea of why some of these are failing, those that have long
VARCHAR columns with output truncated by ij. They contain diffs with an
& that is the truncation indicator. e.g. predicatesIntoViews.

The output contains runtime statistics output which in turn contains the
text of the SQL statement. The String from getString() of this column
output is truncated by ij as it execeeds the specified maxDisplayWidth.

If the text of the SQL statement is multi-line, or maybe just multi-line
with an initial comment (I haven't looked that deeply) then if Derby is
built on Windows that text contains '\r\n' for the new line(s). If Derby
is built on Unix/Linux the new line will be '\n'. Thus the length of the
runtime statistics String is different and truncating results in a
different last line. Note the new-lines in the rest of the
runtime-statistics output are consistently '\n'.
The actual bug for this could be in reading the script file in ij, how
ij parses SQL statements and passes them onto the engine, or how the
engine obtains the text of the SQL statement for runtime stats.

A quick workaround is to increase the max display width on those tests
to avoid the problem. I will try that and see how many of these tests
will pass that way.

Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


View raw message