Bug #42532 IBMDB2i doesn't throw ER_DUP_ENTRY, where it is expected to throw

• Submitted: 2 Feb 2009 6:16
• Modified: 2 Feb 2013 11:27
• Reporter: Nirbhay Choubey
• Status: Unsupported
• Category: Obsolete
• Severity: S3 (Non-critical)
• Version: 5.1.30
• OS: Other (IBMi 5.4)
• Assigned to: Assigned Account
• CPU Architecture: Any

[2 Feb 2009 6:16] Nirbhay Choubey

Description:
Follow the statements :

mysql> create table t1(a int not null auto_increment primary key, val int);
Query OK, 0 rows affected (0.10 sec)

mysql> insert into t1 (val) values (1);
Query OK, 1 row affected (0.01 sec)

mysql> select * from t1;
+---+------+
| a | val  |
+---+------+
| 1 |    1 |
+---+------+
1 row in set (0.01 sec)

mysql> update t1 set a=2 where a=1;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> select * from t1;
+---+------+
| a | val  |
+---+------+
| 2 |    1 |
+---+------+
1 row in set (0.01 sec)

mysql> insert into t1 (val) values (1); # Here it is expected to throw 
                                        #ER_DUP_ENTRY as ibmdb2i does 
                                        #not update the counter.
Query OK, 1 row affected (0.35 sec)

mysql> select * from t1;
+---+------+
| a | val  |
+---+------+
| 2 |    1 |
| 3 |    1 |
+---+------+
2 rows in set (0.00 sec)

How to repeat:
See the above description.

[2 Feb 2013 11:27] MySQL Verification Team

as far as I know we don't support db2 plugin anymore.