Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
Defect Description:
In JDBCT4 driver, the first case is to start 1 thread to check the default increment of primary key that will be equal to 1, the second case is to start 10 threads to check the default increment of primary key that will be changed to 25, in general, the default increment of primary key will be changed according to the difference threads' number.
Test Environment:
DB cluster: 16.235.158.113:37800
Username and Password: trafodion/traf123
DCS Severs' number: 72
Test Steps:
Step1. drop the table if exists, the SQL statement as below,
"drop table if exists JDBCT4_TAB_SIMPLEINTERACTIVESQLSTMT"
Step2. create a table to prepare to test, the SQL statement as below,
"create table JDBCT4_TAB_SIMPLEINTERACTIVESQLSTMT(c1 largeint generated by default as identity, c2 int, c3 varchar(20), primary key(c1))"
Step3. for each thread, write a function to insert several rows into the table, the SQL statement as below (tId: the current thread name that is set to a integer value),
"insert into JDBCT4_TAB_SIMPLEINTERACTIVESQLSTMT(c2, c3) values(" + tId + ", 'thread" + tId + "')"
Step4. Start 1 thread, login TRAFCI to observe the default increment of primary key "c1", actual value is 1, and the seed is 1.
Step5. Start 10 threads, login HPDCI to observe the default increment of primary key "c1", actual value is 25, and the seed is 1.
BTW, in ODBC driver, this issue still exists.