Postgres constraint references

Question

When defining a field, what is the difference between:

,cadastre           integer NOT NULL

,CONSTRAINT fkey_affaire_vl_cadastre FOREIGN KEY(cadastre)
    REFERENCES public.vl_cadastre (obj_id) MATCH SIMPLE
    ON UPDATE RESTRICT ON DELETE RESTRICT

AND directly

,cadastre           integer NOT NULL REFERENCES public.cadastre (obj_id)

GMB · Accepted Answer · 2020-10-16 12:39:11Z

2

Both constructs do create a foreign key. The short expression is called an inline foreign key.

The main difference is that the long expression allows you to choose the name of the constraint, while the first one doesn't. This is handy if you need to later on manipulate the constraint (say, drop it), since you know its name beforehand.

In your code, the first example uses options on update restrict and on delete restrict. This is also supported in the inline form of a foreign key declaration.

answered Oct 16, 2020 at 12:39

GMB

224k25 gold badges103 silver badges151 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Postgres constraint references

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related