Re: ODBC Permissions vs. Application Permissions

If I understand it correctly you only want selects to get through and not let the user accidently change any data.. One of the ways you could do this is by using the sequelink solution from merant. This piece of middleware has an option called readonly. With this the internal parser will only let select statements pass and will not send the inserts/updates/deletes to the database.

Toffie.

In article <z%7Q2.545$xI5.19632_at_typhoon.nycap.rr.com>,   "Louise Weiler" <ljweiler_at_nycap.rr.com> wrote:
> The following scenario/questions have been posed to our DBA's, and we're all
> drawing a blank.
>
> The application that I have written creates specific views of the base
> tables, and then grants a role to a user when the user is created based on
> the ways they can see the data (views). Then, no matter HOW they access the
> data (through the application, through SQL*Plus, through Excel using ODBC)
> they can see and manipulate the same data the same way (i.e., any data they
> can update through the application they can update through SQL*Plus or
> Excel).
>
> BUT, what if we want to only let people QUERY through third party products,
> but still have update/insert/delete capabilities within the application? Is
> there a way to do this (without doing the set role command within the
> application)?
>
> Thanks!
> Louise
>
> --
> -- Louise
> Louise J Weiler
> Ballston Lake, NY
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon Apr 12 1999 - 08:19:02 CDT