Hi Sean / *, Am 29.11.2011 22:47, schrieb Leyne, Sean: > Again, though how would that be done in SQL?
right - the original question was: can direct modification of system tables be completely disabled, and (if yes): what alternatives would we need...to still be able to do what we do nowadays _with_ those direct modifications. Afaikt we all agree that those direct updates should be disabled completely, if possible. Using the API is one thing, but imho it should be possible to do all of that from within a SQL script - like DROP SOURCE OF [<procedure name>|<trigger name>|*] or CHANGE OWNER OF [<db object>|*] TO <new_owner> - along these lines. ( Security/grants will have to be carefully considered here, obviously! :-) ) Does the "standard" say anything about these things? cheers, Frank ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
