> -----Original Message----- > From: Frank Ingermann [mailto:fr...@fingerman.de] > Sent: Miércoles, 30 de Noviembre de 2011 19:32 > > Still i think it's a no-go to just take the ability _away_ to > clear out those sources. It IS common practise.
I don't see any reason to forbid it either. Let's see COMMENT ON DATABASE IS <value | null> merely affects the single record in rdb$database. But we can reuse reserved words to make clearer the purpose of the command as opposed to affecting a single object. Looking at our existing tokens, I can produce a wild syntax: COMMENT OVER ALL DATABASE IS <value | null> or simply leave the oly option to be COMMENT OVER ALL DATABASE IS NULL because I think the typical option is to clear comments, not to put something silly instead. 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. ALTER DATABASE STOP DEBUGINFO -> do not log debug information anymore. C. ------------------------------------------------------------------------------ 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
