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

Re: constraints and sql92 information_schema compliance

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: andrew(at)supernews(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: constraints and sql92 information_schema compliance
Date: 2006-02-27 19:20:55
Message-ID: 44035117.2090903@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Andrew - Supernews wrote:

>On 2006-02-27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>  
>
>>I do have doubts about adding any large number of add-on views to
>>pg_catalog, because of the privileged place of that schema in search
>>paths.  It'd be better to put them in a separate schema ("pg_info"
>>maybe?) where they'd pose less risk of conflicts with user-defined names.
>>Does newsysviews already do this?
>>    
>>
>
>The current version in pgfoundry CVS uses "pg_sysviews" as the schema name.
>If you have any better suggestions for the name, or any other aspect of the
>project, then we're all ears.
>
>  
>
How fine-grained do we want to get on namespaces? I'd be slightly more 
inclined to have pg_info or maybe pg_utils as a place to stash not only 
extra system views but other utility stuff that we want to ship but is 
essentially droppable.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2006-02-27 19:24:05
Subject: Re: constraints and sql92 information_schema compliance
Previous:From: Tom LaneDate: 2006-02-27 19:17:03
Subject: Re: constraints and sql92 information_schema compliance

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