> >> The attached patch allows SET CONSTRAINTS to take a schema
qualified
> >> constraint name (myschema.t1_fk_t2) and when given a bare
constraint name
> >> it uses the search_path to determine the matching constraint
instead of
> >> the previous behavior of disabling all identically named
constraints.
> >
> > This patch seems egregiously non backwards compatible :-(.
>
> Yes, it does change the existing behavior, but "egregiously"? How many
> applications intentionally defer constraints in multiple schemas at
once?
intentionally defer "specifically named" constraints in multiple schemas
(The default application would imho eighter defer all, or a specific
constraint)
> Not many. I would guess the more likely situation is that these
> applications don't even realize that they are deferring more than one
> constraint when it happens.
I agree. I think the new behavior is more intuitive, and would even
argue
the old behavior gets it wrong.
Andreas