Dimitar Pankov
Dimitar Pankov
> Both LEFT JOINs are converted into INNER here, so the optimizer attempts to evaluate possible table permutations. Condition `0+ih.createempid = 999999` significantly reduces the expected cardinality, thus IH is...
Тhe question is why is FB5 trying to change the JOINs from LEFT OUTER to INNER ones and is there any way we can force it NOT to do it?...
Yes, this configuration option will be very useful for us and we are really looking forward for you releasing a version that supports it. In the mean time we hope...
yes, that's absolutely right and that's exactly the reason why we did our best to "hint" the optimizer not to try to use this field/index (by using the 0+ih.CreateEmpID syntax)...
> You can try to create a partial index to replace the existing one. > > ```sql > drop index invoicehbyparentinvoiceiddesc; > > create descending index invoicehbyparentinvoiceiddesc > on invoiceh...
Great, thank you. In the meantime is there by any chance a configuration option in FB5 that we can use to switch back to the old implementation?
@dyemanov, Did you manage to have a look at this issue? Is there any chance you will release a fix soon? This regression stops us from migrating to FB5 and...