Subject Re: [Firebird-Architect] External engines - metadata
Author Adriano dos Santos Fernandes
Vlad Khorsun escreveu:
> This tables was introduces and made non-system because we needed
> compatibility at ODS level in Fyracle. In Firebird we free to modify existing
> system tables as we need. Therefore i fully agreed with changes you
> offer ;)
Good. ;-)

> Our main problem is to define - what is LANGUAGE ? In current implementation
> it is just a plugin identifier without any language semantic.
Config file defines association of language with libraries:

<engine_module myengine>
#engine configuration
filename $(this)/plugins/myengine

<language java>
engine_module myengine

Plugin is located based on RDB$LANGUAGE.

I see not wrong here. This is exactly how INTL works and I'm quite
satisfied with this. :-)

> Also i offer to define interface for external aggregate functions and add in-engine support for them.
I see no conflict about this.

But I think we can define aggregate functions using a generic function.

That mean, it will work with stored functions and will work with
external functions the same way we have stored procedures and external