We are using this for all commands because developer are lazy.
Together with explicit prepare, no possible performance loss, just memory.
But I'm not sure for commands without prepare.
If I remember API, there is possibility to execute SQL without prepare.
And in this case, the first time will be
Sound interesting to have in the provider.
Is this only for commands that has Prepare() explicitly called on?
Is there a scenario where performance will be slower than currently?
On 29 March 2017 at 11:58, Slavomir Skopalik wrote:
> Hi all,
>
> after discussion with Jiri Cincura I prepare propo
Hi all,
after discussion with Jiri Cincura I prepare proposal for prepared
statement cache that will be implemented inside .NET provider.
Motivation:
Preparation of SQL statement take a time and also server resources. Many
SQL server has this functionality build in in engine, but FB not.
More
