View Incident Report

Serious

Reported By: Christian Sanggaard
Reported On: 1/21/2016
For: Version 2.21 Build 1

# 4356 Altering a Primary Key Constraint and Dropping the Last Column Can Corrupt the Key Index

Try to complete the following alter statement. I know that there will be a Key violations, however, the system does not warn you about it or delete records that conflicts. Instead, the table is corrupt after executing.

ALTER TABLE "New Table2"
ALTER CONSTRAINT "PrimaryKey" AS PRIMARY KEY ("Test1"),
DROP COLUMN "Test2"

Comments

The problem was that EDB wasn't rebuilding the internal index that is used to support the primary key constraint.

Resolution

Fixed Problem on 1/22/2016 in version 2.22 build 1

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap