Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!oliveb!pyramid!infmx!aland
From: aland@infmx.UUCP (Dr. Scump)
Newsgroups: comp.databases
Subject: Ads (Was: Restricting access to Informix tables)
Message-ID: <1459@infmx.UUCP>
Date: 29 May 89 06:43:33 GMT
References: <1347@infmx.UUCP> <585@cullsj.UUCP>
Reply-To: aland@infmx.UUCP (alan denney)
Organization: Flight 1523 Survivor's Club
Lines: 25

In article <585@cullsj.UUCP> gupta@cullsj.UUCP (Yogesh Gupta) writes:
>In article <1347@infmx.UUCP>, aland@infmx.UUCP (Dr. Scump) writes:
>< 
>< As I see it, a better route would be to be able to grant permissions
>< to *applications*, like "Application Plans" in DB2.
>< 
><     Alan S. Denney  @  Informix Software, Inc.    
>
>Yes, that is extremely useful.  And you can do exaclty that with Cullinet's
>Enterprise:DB.  It allows the owner of a program to grant EXECUTE authority
>on a program, even though the person executing it might not have any other
>authority.  Also, since our application builder generates applications
>that are no different from user written applications, you can authorize
>them similarly.

If you must use this forum for advertisements, please leave my name
out of such postings in the future.  Thank you very much.

--
    Alan S. Denney  @  Informix Software, Inc.    
         {pyramid|uunet}!infmx!aland                 "I want to live!
   --------------------------------------------       as an honest man,
    Disclaimer:  These opinions are mine alone.       to get all I deserve
    If I am caught or killed, the secretary           and to give all I can."
    will disavow any knowledge of my actions.             - S. Vega