[
https://issues.apache.org/jira/browse/DERBY-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunitha Kambhampati updated DERBY-2278:
---------------------------------------
Attachment: derby2278.p1.diff.txt
Attaching a patch (derby2278.p1.diff.txT) to get feedback.
This patch does the following:
-- Adds a new class OEChecks that does the cardinality checks in order to
separate out the OE code logic into its own class and separating it out from
the junit test framework that we have. This leads to modification in
implementation of the fixtures in the Checks.java to appropriately call the
methods from the OEChecks.
-- Adds a new class - DriverUtility that can be used to populate the OE
database given the drivername and the database connection url and then perform
checks on it.
I tested it against derby as well as a db2 database.
Assumption is that the schema is already loaded into the database.
E.g.
java org.apache.derbyTesting.system.oe.run.DriverUtility -scale 1 -driver
com.ibm.db2.jcc.DB2Driver -dbUrl
'jdbc:db2://localhost:50000/abcdb:user=db2admin;password=spec2001j;' -doChecks
true
svn stat
A java\testing\org\apache\derbyTesting\system\oe\run\DriverUtility.java
M java\testing\org\apache\derbyTesting\system\oe\run\Checks.java
A java\testing\org\apache\derbyTesting\system\oe\util\OEChecks.java
There are some more checks (testCondition1 to testCondition4) existing in the
Checks class. If this approach in this patch seems reasonable, then I'll move
the remaining consistency methods to OEChecks.
Comments/thoughts?
Thanks,
Sunitha.
> Add a generic utility tool to drive the Order Entry load phase.
> ---------------------------------------------------------------
>
> Key: DERBY-2278
> URL: https://issues.apache.org/jira/browse/DERBY-2278
> Project: Derby
> Issue Type: Improvement
> Components: Performance, Test
> Reporter: Sunitha Kambhampati
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2278.p1.diff.txt
>
>
> Add a generic utility program that can take in the driver name and the
> database connection url to populate the order entry database. Currently the
> load phase for OE is completed and hence this driver program should allow one
> to be able to populate the database.
> Maybe once OE run is completed, we can add the driving of the transactions
> also.
> This driver can be in org.apache.derbyTesting.system.oe.run
> see DERBY-1987 and sub-tasks for details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
