Someday, we may start converting legacy tests to an assertion-based
model. When we do that, I recommend starting with these tests which have
generated a spray of different canons for different platforms.
Regards,
-Rick
Knut Anders Hatlen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-925?page=comments#action_12368710 ]
Knut Anders Hatlen commented on DERBY-925:
------------------------------------------
Keeping the master files unmodified is not very important. If the output is
different with the JDBC 3.0 driver and the JDBC 4.0 driver, you don't have to
modify the master files, but you'll have to duplicate them to make derbyall
succeed under JVM 1.6.
Implement new JDBC 4 metadata API getFunctionParameters()
---------------------------------------------------------
Key: DERBY-925
URL: http://issues.apache.org/jira/browse/DERBY-925
Project: Derby
Type: New Feature
Components: JDBC
Versions: 10.2.0.0
Environment: JDK 1.6
Reporter: David Van Couvering
Assignee: Dyre Tjeldvoll
Attachments: TypePrinter.java
I am currently implementing this to return an empty result set so at least
we're compliant, but we should be able to provide real metadata here.
