11.05.2020 12:13, Jiří Činčura wrote:
Hi,
I'm wondering whether it would make sense from engine's POV to have an ability
for the external engine plugin to provide default/implicit/built-in functions -
aka function that are always available (like built-in) and do not require
registration (by using create function/procedure/...) in the database?
Obviously these functions will be limited (mostly I think because of
dependencies), but even with that it's still worthy from my POV.
Looking for ideas and arguments... :)
Look like you want to invent some kind of extensions ;)
To make it work, engine should know about plugins that contain
such extension and list of routimes with its call signatures.
I.e. some kind of metadata.
First task could be solved using standard configuration file -
i.e. admin must add name of plugin to the corresponding setting.
Second task could be solved introducing new interface that
plugin should implement and engine use\consume.
One more task is to make our SQL parser know about extensions.
Am I missing something ?
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
