So forget the previous discussion for a moment. Especially any parts about
the best ways to implement replication and SELECT * problems.
Without getting into the details of the use case, essentially the OP asked
for a way to suppress the presence of selected fields in tables. 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. If that was the
specific proposal, would you all say "the feature should not be
implemented"?
------------------------------------------------------------------------------
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
