29.11.2011 9:01, Dmitry Yemanov wrote: > Frank has shown a somewhat similar one: it's a more or less common > practice to empty/nullify the RDB$***_SOURCE columns. > > So perhaps, unless some good alternative can be offered, we could still > allow modifications of particular columns that are known to not affect > the metadata stability. Both descriptions and SQL sources do belong to > this list, I suppose.
Shouldn't RDB$%_SOURCE fields not to be accessible at all? Practice to nullify such fields was born from the inability to protect them from public reading. -- SY, SD. ------------------------------------------------------------------------------ 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
