Re: SET CONSTRAINTS not schema-aware

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruno Wolff III <bruno(at)wolff(dot)to>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET CONSTRAINTS not schema-aware
Date: 2003-05-12 10:04:44
Message-ID: Pine.LNX.4.44.0305121203280.6441-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> Yeah. We had that discussion at some point during the 7.3 development
> cycle, and concluded we liked table-local naming for constraints better
> than the SQL spec's global constraint names.

Then why does pg_constraint store a schema OID? The comments say it's for
SQL compatibility, so where else does it need to be compatible besides
this case?

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message geekmalda 2003-05-12 12:34:32 unsubscribe-pattern-allmatching greenback frog
Previous Message Manfred Koizar 2003-05-12 06:53:02 Re: Static snapshot data