|
Problem IT37886
|
Status: Closed |
ADDING A PRIMARY KEY CONSTRAINT AGAINST AN EXISTING NOT NULL SERIAL UNIQUE INDEX INCORRECTLY PERFORMS INTEGRITY CHECKING
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
Given the following schema of a populated table:
create table table1 (col1 serial not null, col2 int not null);
create unique index table1_pk_idx on table1(col1) in
dbspace2k_1;
The addition of a PRIMARY key constraint, as below, should not
perform any integrity checking and complete quickly as there is
an existing UNIQUE index on the SERIAL column which is specified
as NOT NULL.
alter table table1 add constraint primary key (col1) constraint
table1_pk;
If the constraint addition is performed against a highly
populated table, this can result in concurrency problems during
the time the unnecessary integrity checking is being performed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC7. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC7. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC16 and 14.10.xC7. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.08.2021
01.05.2023
01.05.2023 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
