db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5391) The syscs_diag.error_log_reader() vti does not work on derby error logs created since 10.7.1
Date Fri, 26 Aug 2011 13:15:30 GMT
The syscs_diag.error_log_reader() vti does not work on derby error logs created since 10.7.1
--------------------------------------------------------------------------------------------

                 Key: DERBY-5391
                 URL: https://issues.apache.org/jira/browse/DERBY-5391
             Project: Derby
          Issue Type: Bug
          Components: SQL
    Affects Versions: 10.8.1.2, 10.7.1.1, 10.9.0.0
            Reporter: Rick Hillegas


The format of timestamps in Derby logs seems to have changed. As a result, the ErrorLogReader
vti can't parse the text of derby.log. That vti is looking for the literal string "GMT" in
order to locate timestamps.

To reproduce the problem, run ij with -Dderby.language.logStatementText=true and issue the
following query:

  select * from table (syscs_diag.error_log_reader( )) as t1;

You will get an empty result.

This regression was not caught by our tests because SysDiagVTIMappingTest uses a hardcoded
derby.log created by version "10.3.0.0 alpha".

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message