It would be nice if there was an option for visibility ie
GRANT VISIBLE FOR <OBJECT TYPE> <OBJECT> TO [USER|ROLE] <user/role name>
[with grant option];
REVOKE VISIBLE FOR <OBJECT TYPE> <OBJECT> FROM [USER|ROLE] <user/role name>;
With a default of all things being visible to maintain backwards
compatibility, but, allowing the developer to remove sql objects from being
automatically shown to users.
Many times, a developer will create underlying structures that are used for
internal code but not for end users to directly address.
This would prevent users from being inundated with lists of
tables/views/procedures that they have rights to but, would never use
except via developer produced tools.
On 14 July 2014 05:43, Roman Simakov <roman.sima...@gmail.com> wrote:
> 2014-07-14 10:18 GMT+04:00 Simonov Denis <sim-m...@list.ru>:
> > I think it is more correct to describe it as
>
> Agreed.
>
> --
> Roman Simakov
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck®
> Code Sight™ - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck®
Code Sight™ - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
