Re: BUG #1937: Parts of information_schema only accessible to owner - Mailing list pgsql-bugs

From Tony Marston
Subject Re: BUG #1937: Parts of information_schema only accessible to owner
Date
Msg-id 000201c5ccb9$10db9810$c800a8c0@ajmnotebook
Whole thread Raw
In response to BUG #1937: Parts of information_schema only accessible to owner  ("Tony Marston" <tony@marston-home.demon.co.uk>)
List pgsql-bugs
> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e@gmx.net]=20
> Sent: 08 October 2005 14:09
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1937: Parts of information_schema=20
> only accessible to owner
>=20
>=20
> Please copy replies to the mailing list.
>=20
> Tony Marston wrote:
> > I have searched through the SQL 2003 standard and can find no such=20
> > restriction. In the volume titled "Information and=20
> Definition Schemas=20
> > (SQL/Schemata)" in section 5.20 (INORMATON_SCHEMA.COLUMNS view) it=20
> > states the following under the heading "Function":
> >
> > "Identify the columns of tables defined in this catalog that are=20
> > accessible to a given user or role."
>=20
> The information schema currently follows SQL 1999.=20=20
> Interestingly, the=20
> requirement to "blank out" the column defaults of non-owned=20
> tables was=20
> apparently dropped in SQL 2003.  Clearly, we need to review the=20
> information schema for SQL 2003 conformance.

In the mean time I have amended my version of the INFORMATION_SCHEMA.COLUMNS
view to conform to the 2003 standard, so this is now a non-problem for me. I
just thought that I should bring this discrepancy between the 1999 and 2003
standards to your attention.

Tony Marston

http://www.tonymarston.net=20

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #1947: Enhancement Request - CONCAT() function
Next
From: "Tony Marston"
Date:
Subject: Re: BUG #1947: Enhancement Request - CONCAT() function