Re: [PATCHES] schema-qualified SET CONSTRAINTS

2006-04-26 Thread Bruce Momjian 

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
  EnterpriseDBhttp://www.enterprisedb.com

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

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org

Re: [PATCHES] schema-qualified SET CONSTRAINTS

2006-04-17 Thread Bruce Momjian 

Based on discussion, it seems the idea of using search path seems
accepted.

Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---


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
  EnterpriseDBhttp://www.enterprisedb.com

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

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly