On 29-11-2011 19:47, Leyne, Sean wrote:
> Adriano,
>
>> I thing something like:
>>
>> firebird.set_comment(<object type>, <object name>, <comment>)
>
> Seems fine to me. But how would that be done in SQL statement, without
> direct manipulation of the system tables?
>
>
BTW, "FIREBIRD" seems a not good name for that. Better reserve it for
the internal namespace, and use something like "FB_METADATA" for the
package name. Or even a "FB" namespace with "METADATA" package, which
would be easily to use as qualified name.
>> firebird.set_source(<object type>, <object name>, <source>)
>
> This would allow for a user to set the source to be any value (= "Hello
> World"). {I have never tried it, do we currently support, source = "Hello
> World"?}
>
Of course.
>
> I would have thought that the more appropriate operation would have been:
>
> firebird.clear_source(<object type>, <object name>)
>
>
Don't think so. External routines can also have they source set for
anything that has a meaning externally.
> Again, though how would that be done in SQL?
>
>
This will be a system package, with code running like current one who
changes and will continue changing system tables.
The question is if this will be like current system functions (without
metadata) or with metadata in the system tables.
Adriano
------------------------------------------------------------------------------
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
