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

Re: constraints and sql92 information_schema compliance

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: "Clark C(dot) Evans" <cce(at)clarkevans(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: constraints and sql92 information_schema compliance
Date: 2006-02-25 19:41:40
Message-ID: 20060225194140.GA15116@wolff.to (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Feb 24, 2006 at 19:40:33 -0500,
  "Clark C. Evans" <cce(at)clarkevans(dot)com> wrote:
> 
> While the textual description of this view "Identify domain constraints
> in this catalog accessable to a given user." has not changed between
> SQL-1992 and SQL-2003, the actual critera specified is quite different:
> In SQL 1992, it seems to show only domains that are in schemas owned by
> the current user.  In SQL 2003, it seems to be more intelligent: showing
> all constraints that are visible to the current user.  I'm curious which
> rule PostgreSQL's information_schema is using?  I think the SQL-2003
> rules more properly follow the textual description and are more useful;
> the SQL-1999 rules are effectively useless in all but trivial cases.

This has been discussed previously in a couple of threads. I believe the
desire is to make it work as specified in SQL-2003, but I do not remember
whether or not anyone volunteered to do the work to make it happen.

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2006-02-25 19:51:55
Subject: Re: constraints and sql92 information_schema compliance
Previous:From: Jaime CasanovaDate: 2006-02-25 18:15:04
Subject: Re: textToQualifiedNameList second parameter

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