On 04/05/13 07:50, Dmitry Yemanov wrote: > 05.04.2013 5:53, Doug Chamberlin wrote: > >> Seems to me the leading solution would be to extend SQL compliance for >> permissions on fields to the SELECT statement such that users would not >> be able to SELECT fields for which they did not have permission. > Thinking twice, I see that it's not going to hide anything for > applications running as SYSDBA/RDB$ADMIN as we don't check permissions > for them. >
But if we forget about hiding something from people - is not it useful to change behavior of 'select *' in a case when some fields are not selectable? ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
