At 10:50 PM 30/11/2011, Adriano dos Santos Fernandes wrote: >On 30/11/2011 03:53, Alex Peshkoff wrote: >> On 11/30/11 02:42, Frank Ingermann wrote: >>> DROP SOURCE OF [<procedure name>|<trigger name>|*] >>> or >>> CHANGE OWNER OF [<db object>|*] TO<new_owner> >> This approach looks much better than use of system package. >> >> >I don't think bloat the language with non-standard syntax for >non-mainstream tasks is a good thing.
+1 It could be made quite consistent with other ALTER syntax we use already to "change" the character of objects without affecting the internal metadata, viz., ALTER <procedure name>|<trigger name> SET SOURCE NULL ALTER <object name> SET OWNER = <user-name> Incidentally, if some kind of "change owner" feature is added, it should be severely restricted to SYSDBA only, IMO, since no check is done to determine whether any user exists in the security DB -- although perhaps that improvement might be made possible in v.3 with the advent of the database-level security db's? Helen ------------------------------------------------------------------------------ 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
