| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Subject: | schema-qualified SET CONSTRAINTS |
| Date: | 2006-04-11 00:05:09 |
| Message-ID: | Pine.BSO.4.63.0604101902450.24976@leary2.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
Kris Jurka
| Attachment | Content-Type | Size |
|---|---|---|
| set-constraints-schema.patch | text/plain | 10.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew - Supernews | 2006-04-11 00:36:06 | plpgsql by default (was: Re: Remote administration contrib module) |
| Previous Message | Dave Page | 2006-04-10 22:09:47 | Re: Remote administration contrib module |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-11 02:35:44 | Re: schema-qualified SET CONSTRAINTS |
| Previous Message | Luke Lonergan | 2006-04-10 19:09:26 | Re: Support Parallel Query Execution in Executor |