Re: [Firebird-devel] NULL parameter passing for EXECUTE BLOCK statement (FB 2.0)

[Olivier M. <om-...@ti...>]

Hi all,

Le 27 mars 06 =E0 19:37, Greg Strauss a =E9crit :

> When I make a call to isc_dsql_describe_bind(), the XSQLVAR sqltype
> values that are returned do not have the null indicator flag set. Is
> this by design? To me, it looks like an oversight.

I would add two other possible oversights to this wagon.

1) The same thing happens for ordinary EXECUTE PROCEDURE statements. =20
The XSQLVAR sqltype values do not reflect that the null indicator =20
might be set on the input parameters.

2) In case of the EXECUTE BLOCK statement, there is another small =20
problem, the isc_info_sql_stmt_type returned by a call to =20
isc_dsql_sql_info declares such an EXECUTE BLOCK statement as being =20
an isc_info_sql_stmt_select. Is this really by design or oversight?  =20
Wouldn't it be better to return at least =20
isc_info_sql_stmt_exec_procedure if not a whole new distinct code?

--=20
Olivier Mascia