ng
informative feedback on business rule violations, complementing the existing
capability in triggers.
Two different tools that can do the same job. One with structure and one
customizable. Because triggers exist the proposed feature is less useful.
Best regards,
Miguel Ferreira
hen I have to write the same rule
twice, in CHECK and TRIGGER, which is redundant.
Best regards,
Miguel Ferreira
PostgreSQL Project Leaders,
Currently, when a CHECK constraint is violated, PostgreSQL returns a generic
error message that includes the constraint name. While informative for
developers familiar with the database schema, this message can be less clear
for other team members, end-users, or i
