Skip site navigation (1) Skip section navigation (2)

Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Proposal for new pgsqlODBC feature - hiding tables inaccessible to the current user
Date: 2007-06-20 14:47:48
Message-ID: 46793E14.6070200@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
Sorry for the late reply.

Mark Cave-Ayland wrote:
> On Thu, 2007-06-07 at 17:13 +0100, Mark Cave-Ayland wrote:
>> Hi everyone,
>>
>> I've just completed the patch for only listing tables accessible by the
>> current user for psqlodbc as detailed in my email here:
>> http://archives.postgresql.org/pgsql-odbc/2007-05/msg00068.php. As
>> suggested in the original post, I have implemented a tick box called
>> "Only list user-accessible tables" on page 2 of the Datasource Advanced
>> Options dialog.

Recently added boolean options are defined as some bits in Extra Opts.
Is it OK to define the option as a bit in Extra Opts ?

>> When this box is ticked, only tables on which the user
>> has one of SELECT, INSERT, DELETE or UPDATE privileges will appear in
>> the table list for the given DSN.

Isn't it sufficient to chack SELECT privilege only ?

>> I think that this would be a really useful feature to add to the
>> psqlodbc driver, and so I have attached a diff from CVS HEAD. As far as
>> I know, the only part I have missed is adding the tickbox and its
>> corresponding translation to the Japanese version of the dialog in
>> psqlodbc.rc. Please let me know if there is any more work I need to do
>> in order to get this applied.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Phillip KilgoreDate: 2007-06-21 22:01:21
Subject: ODBC call syntax returns 1 column instead of n columns
Previous:From: Thomas MuellerDate: 2007-06-20 13:10:03
Subject: Using the PostgreSQL ODBC driver for another database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group