From: | "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Kris Jurka" <books(at)ejurka(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] schema-qualified SET CONSTRAINTS |
Date: | 2006-04-12 08:57:38 |
Message-ID: | E1539E0ED7043848906A8FF995BDA579F31081@m0143.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> >> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2006-04-12 10:20:25 | Re: RH9 postgresql 8.0.7 rpm |
Previous Message | Richard Huxton | 2006-04-12 08:45:19 | Re: Get explain output of postgresql in Tables |