Re: Filtering DatabaseMetaData to show only the items for which the current user has access

From: danap <danap(at)itstriangle(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, PostgreSQL JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Filtering DatabaseMetaData to show only the items for which the current user has access
Date: 2016-09-13 21:02:55
Message-ID: 57D8697F.4010800@itstriangle.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Vladimir Sitnikov wrote:
> Dave>I think a connection parameter patch might be acceptable.
>
> I think the main question is which filters should be enabled by default.
> For instance: should it list a table that is read-only (i.e. no write grants)?

My application requires access to possible read-only tables to gain
functionality, like for instance creating schema for the database.
I would have to check.

Is it really the functionlity of the JDBC to limit access to the
database? Which is already provided through the DatabaseMetaData.

Filter by default on tables that are not readable or writable is
one thing, but limiting by default read-only tables is going to
possibly limit functionality of clients which depend on these
tables for information.

danap.

>
> However, I think it makes sense to hide those tables by default that are
> completely inaccessible (neither readable, nor writable).
>
> Vladimir

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Pavel Raiskup 2016-09-21 11:20:59 9.4.1211 release?
Previous Message Robert Haas 2016-09-13 18:58:50 Re: Patch: Implement failover on libpq connect level.