Hi Roman,
On 14 July 2014 08:37, Roman Simakov <roman.sima...@gmail.com> wrote:
>
> I do not think that separate operators for these are good. It can lead
> to inconsistence like "user has permissions on object but cannot see
> it".
>
>
Actually, that is preferred. For developers and power users, we can
appreciate seeing everything that we use, but, for the average middle
manager who is accessing the database via excel/odbc, they just get
confused by all the options. If firebird had schema, we could easily
limit the items shown to the user, but, since we do not, to be able to
specify specific views being visible while the rest are not, would make the
end users life far easier.
This is end user quality of experience function vs an operational function,
although it could be expanded to have other uses beyond limiting what is
displayed when using 3rd party tools.
Of coarse, such a feature would not be needed if we had support for schema.
------------------------------------------------------------------------------
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
