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

Re: BUG #6768: Failure in OBDC

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: fabio(dot)lunkes(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6768: Failure in OBDC
Date: 2012-07-27 13:56:07
Message-ID: 50129DF7.6070702@ringerc.id.au (view raw or flat)
Thread:
Lists: pgsql-bugs
On 07/27/2012 07:52 AM, fabio(dot)lunkes(at)gmail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      6768
> Logged by:          Fábio Hentz Lunkes
> Email address:      fabio(dot)lunkes(at)gmail(dot)com
> PostgreSQL version: 9.1.0
> Operating system:   Windows 7
> Description:
>
> Hellow.
> My teste to developer application with Microssoft Access, ODBC and Postgres.
> With grant selet in one field, other fields is revoke permissions, access in
> table with Microsoft Access is not possible. Failure is generate, to
> permission denied. In Microsoft MS Query, no error.

I think you'll need to explain this in a bit more detail, with:

- Table definitions
- The EXACT commands you ran
- The EXACT error messages

As far as I know, running:

   GRANT SELECT on tablename(column) TO user;

shouldn't in any way restrict their existing rights, and the 
documentation backs that up:

http://www.postgresql.org/docs/9.1/static/sql-grant.html

    A user may performSELECT,INSERT, etc. on a column if he holds that
    privilege for either the specific column or its whole table.
    Granting the privilege at the table level and then revoking it for
    one column will not do what you might wish: the table-level grant is
    unaffected by a column-level operation.

... so I think you might need to show what's happening in a bit more detail.

Beware that there isn't a big Microsoft Access community here.

--
Craig Ringer

In response to

Responses

pgsql-bugs by date

Next:From: borisDate: 2012-07-27 14:56:18
Subject: BUG #6774: FOR IN SELECT LOOP ignores ORDER BY
Previous:From: Craig RingerDate: 2012-07-27 13:44:28
Subject: Re: BUG #6763: Severe memory leak with arrays and hstore

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