Michael Van Canneyt wrote:
I do it like that too, because the security model of any RDBM is ridiculous, firebird is no exception. Security must be specified at a functional level, never at the table level.
I'm glad we are not the only ones that think like that. :-)
I tried once at the table level, and ended up giving everybody access to everything, because it's relational and everyone at some point ended up writing in some table. So I dumped that, and implemented a separate security mechanism that looks at functions - what is a person allowed to do ?
We are moving over to exactly the same process. Security moves over to the application (or middle-tier) level. Based on the users security level, things like menu items get disabled or hidden.
I'm glad we are heading in the right direction then... ;-) Regards, - Graeme - _______________________________________________________ fpGUI - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
