Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group