Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: CM8.4.3.201211
-
Fix Version/s: CM8.4.3.201211, CQB8.4.3.201211
-
Component/s: CUBRID Manager
-
Environment:
CM8.4.3.3017
Description
1When there are two tables in two databases.
CREATE TABLE "participant"(
"host_year" integer NOT NULL,
"nation_code" character(3) NOT NULL,
"gold" integer DEFAULT 0,
"silver" integer DEFAULT 0,
"bronze" integer DEFAULT 0,
CONSTRAINT pk_participant_host_year_nation_code PRIMARY KEY("host_year","nation_code"),
FOREIGN KEY ("host_year") REFERENCES "olympic"("host_year") ON DELETE RESTRICT ON UPDATE RESTRICT,
FOREIGN KEY ("nation_code") REFERENCES "nation"("code") ON DELETE RESTRICT ON UPDATE RESTRICT
);
CREATE TABLE "participant"(
"host_year" integer NOT NULL,
"nation_code" character(3) NOT NULL,
"gold" integer DEFAULT 0,
"silver" integer DEFAULT 0,
"bronze" integer DEFAULT 0,
CONSTRAINT pk_participant_host_year_nation_code PRIMARY KEY("host_year","nation_code"),
FOREIGN KEY ("nation_code") REFERENCES "nation"("code") ON DELETE RESTRICT ON UPDATE RESTRICT,
FOREIGN KEY ("host_year") REFERENCES "olympic"("host_year") ON DELETE RESTRICT ON UPDATE RESTRICT
);
Actual result:
They are same. but when compare schema, they will be different.
Fixed, it will sort constraint results by the key name when it execute a query of the system view for fetching foreign key informations.