[ http://issues.apache.org/jira/browse/DERBY-2152?page=all ]
A B updated DERBY-2152:
-----------------------
Attachment: d2152_junit_jdk16_fix.patch
> I got three failures in SysDiagVTIMappingTest when I ran the All suite on a
> clean trunk.
It looks like these same failures also occurred in the nightly test results for
Sun 1.6:
http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/sol/489139-_diff.txt
This looks like a nested exception problem: the ASSERT statement checks for
SQLSTATE 42X62, but that's actually a *nested* SQLSTATE; the top-level error
has SQLSTATE 38000.
My first reaction was that we're seeing a case of DERBY-1440, which seems
particularly likely because the failures only occur when running against the
Derby Client. But that said:
1) When I run the test locally with jdk16, I don't see the failures (which
surprised me).
2) DERBY-1440 only talks about jdk16; it does not mention 1.5. But Knut
Anders reported the failures for 1.5, which is odd.
I'm attaching a patch, d2152_junit_jdk16_fix.patch, that should resolve the
failure for jdk16 (and thus in the nightlies). But that said, I don't
understand why I'm not seeing the failure on my local machine, and I don't
understand why Knut Anders was seeing it with jdk15...?
Note: I'm currently on vacation so I'm not able to investigate this further.
If anyone has a chance to track this down and s/he determines that the attached
patch should in fact be committed, then please commit it! I would commit it
myself, but since I don't understand the two points mentioned above and since I
am not actively monitoring the lists, I don't want to make things worse...
> Support diagnostic vti tables that take parameters, such as SpaceTable
> ----------------------------------------------------------------------
>
> Key: DERBY-2152
> URL: http://issues.apache.org/jira/browse/DERBY-2152
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Daniel John Debrunner
> Assigned To: A B
> Attachments: d2152_engine_v1.patch, d2152_engine_v2.patch,
> d2152_junit_jdk16_fix.patch, d2152_testing_v1.patch, d2152_testing_v2.patch,
> d2152_v1.stat, d2152_v2.stat, junit-errors.txt
>
>
> Expand the work of DERBY-571 to support the remaining diagnostic tables that
> take parameters.
> Syntax would use the table constructor, like (not sure if an 'AS' clause will
> be required:
> select * from TABLE(SYSCS_DIAG.SPACE_TABLE(?, ?))
> Diagnostic VTIs that could be handled this way are:
> ErrorLogReader(String log file name)
> SpaceTable(String tableName)
> SpaceTable(String schemaName, String tableName)
> StatementDuration(String inputFileName)
> This is the second stage mentioned in DERBY-571
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
