| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Benjamin Smith <lists(at)benjamindsmith(dot)com> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: MS Access and field-level permissions? |
| Date: | 2010-08-18 14:21:10 |
| Message-ID: | AANLkTikY1x9nES=5ezYXVF3Q-oaEyf5iZfsnxLc5Q0uR@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Tue, Aug 17, 2010 at 3:50 PM, Benjamin Smith
<lists(at)benjamindsmith(dot)com> wrote:
> We're using field level permissions to restrict what data is accessible over
> ODBC - we're enabling SELECT only and on a restrictive set of fields. But, when
> we try to link up with MS Access, none of the fields are populated. You can see
> the fields, but never the content of the fields.
I've never tried to setup field level permissions on access linked
tables before, so this is news to me. However, I wonder if this
behavior is a result of the way MS-Access implements optimistic
locking. I'll have to do more digging on this subject.
> Similarly, with this configuration, via psql when I run "select * from table"
> where I don't have permissions to all fields in the table, I get a "Permission
> denied" error rather than any content.
This is correct. This is the way it is documented to work since '*'
expands to list every field of the set.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gustavo Pinsard | 2010-08-18 18:37:42 | Silent install - check "I accept the terms..." |
| Previous Message | Albin Blaschka | 2010-08-18 06:29:54 | Re: OpenOffice, Go-OO, ODBC, Offline Data Entry |