Set,
>>
>
> I always think of it the opposite way, that is, in case of a LEFT JOIN that
> the LEFT (inner) table is taken first and then the RIGHT (outer) table.
We agree, except that I used "inner" and "outer" in the opposite sense - brain
like body is on holiday.
Ann
>
> (if you need m
>To understand what's happening, you must look at the plan for the join.
>An outer join forces the order of the operation - outer table first, then
>inner table. Depending on the indexes and indexed conjuncts, the order
>you set in the outer join may lead to a fast join, or not. If outer joins
On Aug 2, 2013, at 11:25 AM, "Louis Kleiman (SSTMS, Inc.)"
wrote:
> But LEFT OUTER JOIN may cause the optimizer to scan through the table for
> which all rows are being included in physical order while the INNER JOIN
> might cause a plan where rows are read based on a scan through an index. If
But LEFT OUTER JOIN may cause the optimizer to scan through the table for
which all rows are being included in physical order while the INNER JOIN
might cause a plan where rows are read based on a scan through an index. If
rows aren't being filtered out, I can see how this might speed up the query
On 2.8.2013 13:59, Alexis Diel wrote:
>
>
> but LEFT JOIN is diferente of JOIN...
> - LEFT JOIN brings all the data filtered from the FROM table, and
> - JOIN brings only the data that have the ON condition in the JOINED table.
Which should make JOIN faster than LEFT JOIN, if anything, because
but LEFT JOIN is diferente of JOIN...
- LEFT JOIN brings all the data filtered from the FROM table, and
- JOIN brings only the data that have the ON condition in the JOINED table.
Att,
Alexis Diel
On Fri, Aug 2, 2013 at 3:43 AM, Josef Kokeš wrote:
> Hi!
>
> For a long time I have been using LE
> Hello Josef,
>
> I've never had that issue using Firebird, but some time ago I had a
> similar behavior with SQL Server and the responsible was a fragmented
> index. May be you should take a look to your indexes design or rebuild
> them via backup/restore.
Hi!
That should not be the case here
gards,
De: Josef Kokeš
Para: Firebird Support
Enviado: Viernes, 2 de agosto, 2013 1:43:35
Asunto: [firebird-support] LEFT JOIN much faster than JOIN
Hi!
For a long time I have been using LEFT JOINs rather than JOINs
everywhere, because of some past experience with Firebird 1.5 that LEFT
JO
Hi!
For a long time I have been using LEFT JOINs rather than JOINs
everywhere, because of some past experience with Firebird 1.5 that LEFT
JOIN is much faster than JOIN, even if I have to use WHERE
key_of_the_joined_table IS NULL afterwards. Today I encountered a case
where this is the case even w
