Hi,

I noticed that the error response for a constraint violation only contains the 
column name for not-null constraints. I'm confused because the field isn't 
present when other types of constraints are triggered, such as unique, foreign 
keys, and check constraints. Was this done intentionally because these other 
constraints may involve multiple columns, while the column_name field expects a 
single column?

I understand that a client can find out which columns are involved by a 
constraint name. Alternatively, should it be made more handy so that the 
column_name field is present for all constraints and includes all involved 
columns?

С уважением,
Архипов Никита

Reply via email to