11.05.2020 15:33, Dimitry Sibiryakov wrote:
11.05.2020 14:24, Vlad Khorsun wrote:
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.
UDRs already provide information about input/output
11.05.2020 14:24, Vlad Khorsun wrote:
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.
UDRs already provide information about input/output parameters. The only missed
interface
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
> Do you propose an automatic registration procedure?
Frankly I don't propose anything implementation-wise. I'm just about gathering
ideas, willingness and maybe understanding the feature more in an open
discussion.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel
>Much better would be if engine ask the plugin for list of provided
> routines and don't
> require the registration at all. But this creates an egg-and-chicken
Sometimes the plugin does not know that in advance. So I suppose the
registration is still a valid path.
> problem: how to find
On 2020-05-11 11: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
11.05.2020 11:13, Jiří Činčura wrote:
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
