[
https://issues.apache.org/jira/browse/DERBY-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094027#comment-13094027
]
Rick Hillegas commented on DERBY-5391:
--------------------------------------
Ported 1162827 from trunk to the 10.7 branch at subversion revision 1163355.
> The syscs_diag.error_log_reader() and syscs_diag.statement_duration() vtis do
> 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.7.1.1, 10.8.1.2, 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: derby-5391-01-aa-fixErrorLogReader.diff,
> derby-5391-01-ac-fixErrorLogReaderAndStatementDuration.diff,
> derby-5391-01-ad-fixErrorLogReaderAndStatementDuration.diff
>
>
> 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".
> The same problem seems to have broken the statement duration vti too. The
> following query returns an empty result from 10.7 onward:
> select * from table (syscs_diag.statement_duration()) as t1;
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
