What is the advantage to the CONSTRAINT clause vs constraints in the table/field definition? For example:

CREATE TABLE "Phone Number" (
"Phone ID" INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 0) NOT NULL PRIMARY KEY,
"Patient ID" INTEGER NOT NULL,
"Number" VARCHAR(10),
"Description" VARCHAR(10),
CONSTRAINT FK_PAT_PHN FOREIGN KEY ("Patient ID") REFERENCES "Patient" ("ID Number")
);

Seems to add no real functionality, but who knows.

Dave

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 1/12/2021 11:21 AM, Dave wrote:

What is the advantage to the CONSTRAINT clause vs constraints in the table/field definition?  For example:

CREATE TABLE "Phone Number" (
"Phone ID" INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 0) NOT NULL PRIMARY KEY,
"Patient ID" INTEGER NOT NULL,
"Number" VARCHAR(10),
"Description" VARCHAR(10),
CONSTRAINT FK_PAT_PHN FOREIGN KEY ("Patient ID") REFERENCES "Patient" ("ID Number")
);

Seems to add no real functionality, but who knows.

Dave

What storage engine are you using?

--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)