So far, there is no official way to hide procedures and triggers source code (protecting intelectual property). The technique of updating system tables writing "null" to the source code is used by a lot of people, since it seems to be the only way to have some kind of protection (ok, BLR can be "understood", but this would required more efforts than usually normal people are willing to do).
Problem is that this technique will not work anymore in Firebird 3. Since there is still no official way to protect/hide the source code, I suggest that the rdb$procedures and rdb$triggers should not become readonly until we have an official way to deal with this problem. I think this is a critical decision that should be discussed now, otherwise we can expect lots of mad users when FB 3 is released. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
