On 8/19/2010 11:48 AM, Kathey Marsden wrote:
I can reproduce the weme problem and am looking at that now.
The weme failure is old and a little hard to track down because we get
no stack trace. I'll file a bug later today if nobody sees something
obvious. Any idea how to get JUnit to give up a stack trace in this
scenario?t to print a stack trace with this?
August 5 was the first time weme failed with this error:
Failed to invoke suite():java.lang.reflect.InvocationTargetException
Below are the checkins that day.
r982585 | rhillegas | 2010-08-05 05:46:51 -0700 (Thu, 05 Aug 2010) | 1 line
Changed paths:
M /db/derby/code/trunk/NOTICE
A /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/HarmonySerial
lob.java
A /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/HarmonySerial
lob.java
M /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/SQLBinary.jav
M /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/SQLBlob.java
M /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/SQLChar.java
M /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/SQLClob.java
DERBY-4754: Make the getObject() methods of Derby's LOBs always return jdbc LOB
.
------------------------------------------------------------------------
r982637 | bpendleton | 2010-08-05 07:25:39 -0700 (Thu, 05 Aug 2010) | 25 lines
Changed paths:
M /db/derby/code/trunk/build.xml
M /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/te
ts/lang/XplainStatisticsTest.java
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/A
cessDatabase.java
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/C
eateHTMLFile.java
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/C
eateXMLFile.java
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/T
eeNode.java
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/r
sources
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/r
sources/advancedViewXSL.xsl
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/r
sources/advancedViewXSL2.xsl
A /db/derby/code/trunk/java/tools/org/apache/derby/impl/tools/planexporter/r
sources/vanilla_html.xsl
A /db/derby/code/trunk/java/tools/org/apache/derby/tools/PlanExporter.java
M /db/derby/code/trunk/tools/jar/tools.properties
DERBY-4587: Add tools for query plan analysis
This patch was contributed by C.S. Nirmal J. Fernando (nirmal070125 at gmail do
com)
This patch adds a new tool, PlanExporter, to derbytools.jar. The PlanExporter
tool's primary purpose is to gather the information about a particular query
execution from the Derby XPLAIN tables, and to format that data into an
export format for usage by other tools. The most important export format is
XML, but the tool can also format the query into HTML or other formats by
running an appropriate XSL Stylesheet across the XML data.
The tool is run as follows:
java org.apache.derby.tools.PlanExporter dbURL username pwd schema stmt_id
-xml outputFileName
This patch includes the tool itself, and changes to the XplainStatisticsTest
to incorporate regression testing of the PlanExporter tool. Documentation of
the new tool is being developed under DERBY-4758.
The basic implementation of the tool is complete and operational, and ready
for use by the Derby community. Depending on community feedback, possible
future enhancements to the tool might include improved formatting stylesheets,
additional output formats, more detailed XML output, etc.
------------------------------------------------------------------------
