Re: constraints and sql92 information_schema compliance

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, "Clark C(dot) Evans" <cce(at)clarkevans(dot)com>, Bruno Wolff III <bruno(at)wolff(dot)to>
Subject: Re: constraints and sql92 information_schema compliance
Date: 2006-02-27 05:03:58
Message-ID: 200602262103.58561.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> No way. The entire point of information_schema is that it is standard;
> adding non-spec things to it renders it no better than direct access
> to the PG catalogs.

Hmmm ... so, per you, we can't add extra views covering non-spec objects to
the information_schema (like aggregates) because we can't modify it in any
way. But per Peter we can't add new views to the pg_catalog because we
want people to use information_schema. I sense a catch-22 here.

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Luke Lonergan 2006-02-27 06:15:06 Re: TOAST compression
Previous Message Josh Berkus 2006-02-27 04:04:09 Re: TOAST compression