Re: SET CONSTRAINTS not schema-aware

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
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 13:44:12
Message-ID: 8589.1052747052@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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?

I think we left it there for possible future use with assertions, which
are not tied to any particular table.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Adam Siegel 2003-05-12 14:51:17 Re: realtime data inserts
Previous Message Tom Lane 2003-05-12 13:40:37 Re: Static snapshot data