[ 
https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465645
 ] 

Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------

It's not so cool that Populate had a CleanDatabaseSetup decorator that cleaned 
up the database, thus dropping all the insert rows. :-) I removed that from the 
commit so I could look at the data.

The loaded data does not match the TPC-C spec in one important factor. In the 
specification identifiers start at 1 (one), e.g. 1-10 for a district 
identifier, but the patch (and committed) code start with 0 (zero), e.g. 0-9 
for district. I know to look out for this because I wasted time once trying to 
figure out why a TPC-A bechmark was not working at a hardware vendor's site. I 
discovered the cause was some of the system was using zero-based identifiers 
and the rest was one-based. :-( In fact double checking the committed code 
seems to be inconsistent, warehouse and district are 0 based but customer is 1 
based, I didn't check the rest.

Committed revision 497297 - Thanks Sunitha

On the load improvements I can't see any need for per-table loading in the 
short term. I can see a near-term requirement for incremental loads, e.g. load 
data for an additional N warehouses. That could be some later improvement.

> 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

        

Reply via email to