Answer the question
In order to leave comments, you need to log in
Is there a consensus on where to check constraint: on the database side or in the application code?
Logically, restrictions on possible data values are part of the data model that is implemented in a particular schema. It turns out that it is more correct to produce a check constraint on the database side.
Is it so? Maybe there is another point of view?
Answer the question
In order to leave comments, you need to log in
There is depends on the system and requirements. There will be no unequivocal answer because everything is always trade-off
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question