That worked perfectly !
Thanks a bunch !
Even with "...AND I.idC IN (1234,1235,1236)" it works as fast as you would expect.
Thanks again for a good workaround !
</A>
The = version works for this particular query, but I have other queries where the sub-SELECT returns more than one result.
For those cases I haven't found a workaround yet.
Tried it on MSSQL - apparently that optimizer does the right thing.
Does anyone know if this is fixed in the commercial...
Thanks for the reply.
After a lot of testing and searching I started to suspect that it had something to do with the optimizer like you say, and I even tried the same thing under the latest Firebird release (1.5) with the same result.
Today I found out that the issue is logged in the Firebird...
I would think the following two queries should be processed the same, but the first one takes over a second, while the second takes a few milliseconds.
SELECT * FROM tblData WHERE idA IN (SELECT idB FROM tblIndex WHERE idC=1234);
SELECT * FROM tblData WHERE idA = (SELECT idB FROM tblIndex...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.