> Can it already attach to the caller's current transaction?
Not exactly, yet.
--
Mgr. Jiří Činčura
Independent IT Specialist
--
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to e
Memory leak when use SHOW GRANTS on new empty database (3.0.1 & 4.0; SS & SC)
--
Key: CORE-5294
URL: http://tracker.firebirdsql.org/browse/CORE-5294
Project: Firebird Core
Em 27/06/2016 15:51, Jiří Činčura escreveu:
> Hi *,
>
> there's something I've been working on for a few evenings and weekends.
> As you might know, from Firebird 3 there's and interface to write a
> plugin that allows to execute any code as stored procedure, function or
> trigger.
>
> So why not
27.06.2016 21:51, Jiří Činčura wrote:
> Hi *,
>
> there's something I've been working on for a few evenings and weekends.
> As you might know, from Firebird 3 there's and interface to write a
> plugin that allows to execute any code as stored procedure, function or
> trigger.
>
> So why not to have
Hi *,
there's something I've been working on for a few evenings and weekends.
As you might know, from Firebird 3 there's and interface to write a
plugin that allows to execute any code as stored procedure, function or
trigger.
So why not to have these in .NET, right? I have a working plugin right
On 27/06/2016 12:14, Jiří Činčura wrote:
> Hi *,
>
> what's the recommended approach for returning error from external engine
> plugin? Something like this is OK?
>
> static const ISC_STATUS statusVector[] = {
> isc_arg_gds, isc_random,
> isc_arg_string, (ISC_STATUS) "Foo Bar",
>
Hi *,
what's the recommended approach for returning error from external engine
plugin? Something like this is OK?
static const ISC_STATUS statusVector[] = {
isc_arg_gds, isc_random,
isc_arg_string, (ISC_STATUS) "Foo Bar",
isc_arg_end
};
throw FbException(status, statusVect
