Hi Claudio, >> From: Frank Ingermann [mailto:fr...@fingerman.de] >> >> Still i think it's a no-go to just take the ability _away_ to >> clear out those sources. It IS common practise.
<snip> (+1 for the COMMENTs!) > The problem is that we lack equivalent commands for sources and debugging. > Then if we want uniformity, what about > > ALTER DATABASE DROP COMMENTS > ALTER DATABASE DROP SOURCES > ALTER DATABASE DROP DEBUGINFO > > Replace DROP by CLEAR if you like. explicit, simple syntax - me likes it! (whether it's DROP <x>, CLEAR <x>, or SET <x> TO NULL... that's really "syntactic sugar" i guess.) 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