Hi, Is there a formal definition for the order in which constraint actions (i.e. the ON DELETE or ON UPDATE rules) are applied when there are multiple overlapping/relevant constraints? I have struggled to find an answer in the manual, but my experiments suggest that they are interpreted in the order in which the constraints were defined and the first rule in this order is applied while subsequent rules are ignored. This can be very confusing if one rule says CASCADE and another NO ACTION, and you need to understand this order of definition to know whether a delete will cascade or raise an error. Is there a definitive way to introspect the informatation_schema or pg_catalog to determine which behaviors will effectively apply to a given "DELETE FROM ..." or "UPDATE ..." statement? Thanks, Karl -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
