Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user - Mailing list pgsql-odbc

From Dave Page
Subject Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user
Date
Msg-id 4683D9A3.7010307@postgresql.org
Whole thread Raw
In response to Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user  (Hiroshi Inoue <inoue@tpf.co.jp>)
Responses Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user  (Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>)
Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user  (Hiroshi Inoue <inoue@tpf.co.jp>)
List pgsql-odbc
Hiroshi Inoue wrote:
> Mark Cave-Ayland wrote:
>> On Wed, 2007-06-27 at 09:01 +0900, Hiroshi Inoue wrote:
>>
>>> How about changing the default behavior of SQLTables to list only
>>> SELECTable tables and add a bit to Extra Opts to list inaccessible
>>> tables also ?
>> I think this would risk breaking a lot of existing applications.
>
> Really ?
> I can hardly imagine the applications which would update/delete
> the rows whose contents couldn't be seen.

insert-only audit tables?

Yes, they should really be handled by server-side triggers, but I know
of at least a couple of apps running on PostgreSQL with psqlODBC that do
it client side.

Regards, Dave

pgsql-odbc by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user
Next
From: Mark Cave-Ayland
Date:
Subject: Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user