> >> 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
constr
On Mon, 10 Apr 2006, Tom Lane wrote:
Kris Jurka <[EMAIL PROTECTED]> writes:
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
th
