Damn. Anyone know why the heck FB won't use an index in a join with 'starting
with'?
FWIW, I ran the natural part of the query to generate a bunch of starting with
'xyx' or and appended them to query the other table. Luckily I didn't hit any
query limits.
-Original Message-
From:
Rick,
It's not going to help in the short run, but I would submit this as a bug.
This query uses natural for both tables, when I expected it to use an
index for the join.
select *
from table1 t1
join table2 t2 on t2.indexed_char14 starting with t1.indexed_char10
where t1.unindex_varchar
From: Rick Debay rde...@accessrxs.com
Damn. Anyone know why the heck FB won't use an index in a join with
'starting with'?
FWIW, I ran the natural part of the query to generate a bunch of starting
with 'xyx' or and appended them to query the other table. Luckily I
didn't hit any query
-- Original Message ---
From: Rick Debay rde...@accessrxs.com
Damn. Anyone know why the heck FB won't use an index in a join with
'starting with'? FWIW, I ran the natural part of the query to generate
a bunch of starting with 'xyx' or and appended them to query the
other
Anyone? Without any indexes, I won't live to see this complete.
-Original Message-
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Rick Debay
Sent: Friday, April 06, 2012 5:18 PM
To: firebird-support@yahoogroups.com
Subject:
This query uses natural for both tables, when I expected it to use an
index for the join.
select *
from table1 t1
join table2 t2 on t2.indexed_char14 starting with t1.indexed_char10
where t1.unindex_varchar containing 'foo'
This uses an index, so the optimizer knows about it.
select *
from
This query uses natural for both tables, when I expected it to use an
index for the join.
select *
from table1 t1
join table2 t2 on t2.indexed_char14 starting with t.indexed_char10
where t.unindex_varchar containing 'foo'
This uses an index, so the optimizer knows about it.
select *
from table2