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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: constraints and sql92 information_schema compliance


  • From: Bruno Wolff III <bruno(at)wolff(dot)to>
  • To: "Clark C. 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: Sat, 25 Feb 2006 13:41:40 -0600
  • Message-id: <20060225194140(dot)GA15116(at)wolff(dot)to>

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.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group