Hi,
what's the reason for IMetadataBuilder parameters in
IExternalEngineImpl::make[Procedure|Function]. I'm asking because using
IRoutineMetadata `metadata->getInputMetadata(status)->getBuilder(status)` seems
to give me same object(s). Or maybe put differently, what's the difference
between `i
Never mind, I think I figured it out. The [in|out]Builder seems to be used
later to provide the message to `execute` method.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 19/09/2019 07:49, Jiří Činčura wrote:
> Hi,
>
> what's the reason for IMetadataBuilder parameters in
> IExternalEngineImpl::make[Procedure|Function]. I'm asking because using
> IRoutineMetadata `metadata->getInputMetadata(status)->getBuilder(status)`
> seems to give me same object(s). Or mayb
Hi
in TraceObjects.cpp in TraceSQLStatementImpl i can access DsqlCompiledStatement
from the m_stmt->getStatement()
and then i can know "Type" e.g. TYPE_SELECT, TYPE_UPDATE, TYPE_DELETE ...
How can i access this info in Monitoring.cpp for MON$STATEMENTS
(Monitoring::dumpAttachment) where i hav
cmd update affect field not in command
--
Key: CORE-6146
URL: http://tracker.firebirdsql.org/browse/CORE-6146
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.4
