be slower than currently?
>
> On 29 March 2017 at 11:58, Slavomir Skopalik wrote:
>
>> Hi all,
>>
>> after discussion with Jiri Cincura I prepare proposal for prepared
>> statement cache that will be implemented inside .NET provider.
>>
>> Motivation:
>
statements.
The question:
Is this interesting to have this functionality inside provider and fully
transparent?
Slavek
PS: We combine this with RO transaction pool and also with data caching,
but this is different story.
--
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s.r.o.
Collection
Hi,
the LIKE statement is very complex and in some cases it can used index.
.. WHERE aaa LIKE 'aaa%'
and in outher not:
... WHERE aaa LIKE '% aaa'
SP must create plan when you are preparing statament and this is before
sending parameters.
In second case, you run SQL on fly and in this case the p
Hi,
this is because LIKE operator in general case CAN'T use a index.
You must equal or other operator instead.
Slavek
PS: Like in this case is dangerou because huge performance penalty
(try use second case with SuchName='%').
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAI
Title: Zpráva
Putting FirebirdSql.Data.Firebird.dll into bin
directory in root of asp net application is enough.
I was
used this dll in many servers (about 10) without problem.
But
I'm using version 1.5.xx of this provider againts FB 1.5.x and
2.0.x.
Framework 1.1 and 2.0, IIS server and Apa
