Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Richard Lewis — — source: Informix-list mailing list archive (1991-1998)
Hi Dave,
We are interested in a solution here too.
How does you solution help ? What is to stop a user entering "SET ROLE
..." from their SQL tool ? They would then have the same access to the
database as via the application. All you could do would be to hide the
definitions of the roles from the users. Is this correct ?
Richard Lewis
Gerling Global Group (Australia)
Dave Otto <dotto@themoneystore.com> wrote in article
<5v4d99$6i5@cssun.mathcs.emory.edu>...
> At 01:06 PM 9/9/97 -0400, Tim Kelly wrote:
> >Now that's what I'm taking about. Now it appears I'm not overlooking
> >some feature to CLI Informix etc. Matter of fact the 2.x ODBC
> >specification doesn't call for anything like this. I also have the same
> >issue with MS SQL-Server and Oracle.
>
> What was described here could quite simply be implemented w/ roles.
> First revoke all access rights from everyone (including public). Then
> set up the roles you need to run the application. The "set role" should
> be the first command issued from the application.
>
> -d
>
>
>
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.