| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Dave Page <dpage(at)postgresql(dot)org> |
| Cc: | Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user |
| Date: | 2007-06-29 00:31:13 |
| Message-ID: | 468452D1.3000009@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Dave Page wrote:
> 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.
Hmm the apps list the tables using SQLTables() ?
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-06-29 07:37:51 | Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user |
| Previous Message | Andreas | 2007-06-29 00:15:38 | Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user |