12.06.2020 9:52, Pavel Cisar wrote:
2. The statement prepare requires active transaction although it's not bound to
one.
The same as ISC API. And this is fully correct. Why do you want to bound
prepared
request to the preparing transaction ?
Regards,
Vlad
Firebird-Devel mailing list, w
Vlad,
I don't want to bound it at all :) Quite the opposite, it would be nice
if statement prepare would NOT require active transaction at all. It
would allow full decoupling of prepare from execution context in
connectivity layer.
I know that engine needs it for some reason (metadata?), but
12.06.2020 08:52, Pavel Cisar wrote:
If you have objections, you should provide a list with reasons why it's bad.
At first, I already did it a lot.
At second now it is pointless because the API already was declared "public" and thus
engraved in stone.
--
WBR, SD.
Firebird-Devel maili
On 12/06/2020 07:16, Dimitry Sibiryakov wrote:
> 12.06.2020 08:52, Pavel Cisar wrote:
>> If you have objections, you should provide a list with reasons why
>> it's bad.
>
> At first, I already did it a lot.
> At second now it is pointless because the API already was declared
> "public" and thus
