On Feb 7, 2008, at 12:39 PM, johnf wrote:
> SELECT table_name,table_schema
> FROM information_schema.tables
> WHERE table_type = 'BASE TABLE'
> AND table_schema NOT IN
> ('pg_catalog', 'information_schema');
>
> 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 did some reading in the Postgres docs, and I couldn't find anything
that corroborated the claim I had heard earlier that
information_schema was not generally accessible to non-privileged
users. The docs confirmed that even with admin privs, you cannot edit
the info in that schema, so there would be no need to restrict write
access, since it's already restricted.
If we can find something that indicates when/if *read* access can be
restricted, we can then make an informed choice of code for getTables().
-- Ed Leafe
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
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]
