|Subject||RE: [firebird-support] Problem with not in queries in Firebird 2.0 RC3|
> It appears to me that if I now attempt to run a query with a not in clausemay
>It's a bugfix, actually. NOT IN and ALL don't use indices anymore, as it
>cause wrong results in some cases (we had three related bugreports). But asThanks for the advice. I am using NOT IN quite frequently in my application
>subqueries still executed per every master row, you'll have a very long
>execution time. Sad but true.
>A workaround is to use a left outer join with IS NULL clause in the WHERE
and I'm glad that I am working towards including firebird 2.0 in the next
This gives me an opportunity to rewrite those queries before release.
Is NOT EXISTS also an option to replace NOT IN in that it will use indices?
[Non-text portions of this message have been removed]