[
https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465636
]
Sunitha Kambhampati commented on DERBY-2095:
--------------------------------------------
Thanks Dan for your comments. I agree the LoadTester is a overkill. I'll clean
it up.
>I like the Load interface as a concept but I'm trying to understand why the
>individual table load methods exist >on it and the rowsInTable method is there?
>
>Seems like the populateAllTables() is sufficient to load the data, when would
>the other methods be called through the interface?
Currently for the Order Entry implementation, populateAllTables will be
sufficient.
My original intention when adding those methods were thinking if this would be
useful for other scenarios/test in the future, thinking more of building blocks
concept for tests.. Does that make sense or do you think this may be just
overkill.. ?
I'll cleanup the SimpleInsert constructor in a followup patch. Thanks.
> Add the ability to populate a database for the order entry toolkit based upon
> the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
