home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!ucbvax!mtxinu!sybase!houdini!jeffl
- From: jeffl@houdini.sybase.com (Jeff Lichtman)
- Newsgroups: comp.databases
- Subject: Re: SYBASE: stored procedures and permissions
- Message-ID: <22815@sybase.sybase.com>
- Date: 26 Aug 92 01:02:10 GMT
- References: <1992Aug14.012728.16969@manitou.cse.dnd.ca>
- Sender: news@Sybase.COM
- Organization: Committee to Increase The Entropy
- Lines: 28
-
- In article <1992Aug14.012728.16969@manitou.cse.dnd.ca>, pburry@manitou.cse.dnd.ca (Paul Burry) writes:
- > If as the dbo I define
- >
- > create proc a as return
- > go
- > create proc b as exec a
- > go
- > grant execute on b to public
- > go
- >
- > then when as myself I try to use 'b', I get an error stating that I do not
- > have execute permission on 'a'.
-
- This is bug #18773. It is fixed in future versions of the SQL Server.
-
- Fodder for the (*&$*&^% news program that refuses to post unless I write
- more than whom I am quoting:
-
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
- ---
- Jeff Lichtman at Sybase
- {mtxinu,pacbell}!sybase!jeffl -or- jeffl@sybase.com
- "Saints should always be judged guilty until they are proved innocent..."
-