Re: schema-qualified SET CONSTRAINTS

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: schema-qualified SET CONSTRAINTS
Date: 2006-04-27 00:34:54
Message-ID: 200604270034.k3R0YsH02869@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Patch applied. Thanks. I also updated our SGML documentation:

The current schema search path is used to find the first matching name
if no schema name is specified.

---------------------------------------------------------------------------

Kris Jurka wrote:
>
> 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

Content-Description:

[ Attachment, skipping... ]

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2006-04-27 01:25:39 Re: GIN - Generalized Inverted iNdex. Try 2.
Previous Message Tom Lane 2006-04-27 00:13:21 Re: ANSI-strict pointer aliasing rules

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-04-27 00:36:45 Re: [PATCH] Remove useless DH param code on client side
Previous Message Bruce Momjian 2006-04-27 00:06:52 Re: pgstat: delayed write of stats file