View Incident Report

Serious

Reported By: Grzegorz Rewucki
Reported On: 11/26/2009
For: Version 2.03 Build 6

# 3109 Self-Referencing Foreign Keys Causing Improper Exceptions

XXX is a table with below fields and constraints. Inserting very first row in such table generates EDBError #1004 from constraint FK_XXX_CN with message:

"The foreign key 1 does not match any existing primary or unique key in the table XXX"

"CzynnoscId" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 0,
INCREMENT BY 1),
"CNId" INTEGER DEFAULT CzynnoscId,
"Name" VARCHAR(40),
CONSTRAINT "PK_XXX" PRIMARY KEY (CzynnoscId),
CONSTRAINT "UC_XXX_CN" UNIQUE (CNId, CzynnoscId),
CONSTRAINT "CK_XXX_CN" CHECK (CNId IS NOT NULL),
CONSTRAINT "FK_XXX_CN" FOREIGN KEY (CNId) REFERENCES "XXX" (CzynnoscId)

Resolution

Fixed Problem on 11/29/2009 in version 2.03 build 7

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 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