On 12-7-2014 16:26, Mark Rotteveel wrote: > I am currently implementing protocol version 11 in Jaybird, and I am > using the .NET provider implementation for reference. > > Looking at the .NET code use of lazy send for op_prepare_statement > *always* returns the allocate response (see > https://sourceforge.net/p/firebird/NETProvider/ci/master/tree/NETProvider/src/FirebirdSql.Data.FirebirdClient/Client/Managed/Version11/GdsStatement.cs#l74 > ) > > Looking at the code in remote\interface.cpp of Firebird 2.5 however it > looks like that is only the case when the statement handle wasn't > allocated yet. > > So what is the 'truth'?
After some fiddling with the implementation it looks like the implementation in the .NET provider is incorrect. In the current implementation, preparing another statement with the same statement handle would block. It probably works by accident as once prepared, the .NET provider doesn't re-prepare (eg with a different statement). Mark -- Mark Rotteveel ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
