On Thursday 07 February 2008 10:04:50 am johnf wrote:
> On Thursday 07 February 2008 09:43:33 am Ed Leafe wrote:
> > On Feb 5, 2008, at 9:10 PM, johnf wrote:
> > > BTW if you use information_schema
> > >
> > > SELECT table_name,table_schema
> > > FROM information_schema.tables
> > > WHERE table_type = 'BASE TABLE'
> > > AND table_schema NOT IN
> > > ('pg_catalog', 'information_schema');
> > >
>
>
> CREATE SCHEMA information_schema
> AUTHORIZATION postgres;
> GRANT ALL ON SCHEMA information_schema TO postgres;
> GRANT USAGE ON SCHEMA information_schema TO public;
I have done some testing on the information_schema. In a normal installation
the information_schema view is set to allow 'public' (a group or role) access
and all users are part of the 'public' group/role. Therefore, all users have
access to information_schema. However, it appears that an adminstrator can
remove 'public' from the information_schema view. But I could not
remove 'public' from the user.
I bet at your new job they have lots of security. Maybe you can test the
select above. I don't see any reason not to use the information_schema view
assuming the access is the only issue.
--
John Fabiani
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
