[#CORE-1752] Results of a join with different collations depend on the execution plan

Firebird Core

Results of a join with different collations depend on the execution plan

Created: 20/Feb/08 01:29 PM Updated: 12/Jul/11 05:46 PM

Component/s:

Engine

Affects Version/s:

2.1 Alpha 1, 2.1 Beta 1, 2.1 Beta 2, 2.1 RC1

Fix Version/s:

2.1.4, 2.5.1, 3.0 Alpha 1

Time Tracking:

Not Specified

File Attachments:

test.fbk (14 kB)

Environment:

Firebird 2.1 RC1, W2K, XP

Issue Links:

Relate

This issue relate to:

~~CORE-3553~~ Nested loop plan is chosen instead of the sort merge for joining independent streams using keys of different types

This issue is related to:

QA-269 Test for CORE-1752

~~CORE-1274~~ Wrong results when PLAN MERGE is chosen and datatypes of the equality predicate arguments are different

Planning Status:

Unspecified

Description

« Hide

with test case, db uses charset ISO8859-1

select a.zeitstempel, b.artikelnr
from t1 a
join t2 b on b.artikelnr = a.artikelnr --collate de_de

gives 5 records

uncomment collate de_de and it gives 9 records, the correct result. Using collate affects the execution plan and enables optimizer to find all matching records.

All

Comments

Work Log

Change History

Version Control

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Volker Rehn added a comment - 20/Feb/08 01:31 PM

connect using charset ISO8859-1

[ Permalink | « Hide ]

Sean Leyne added a comment - 20/Feb/08 03:31 PM

Volker,

Why would you add a collate to a JOIN?

[ Permalink | « Hide ]

Kuznetsov Eugene added a comment - 21/Feb/08 12:21 AM

It seems, it's special case of ~~CORE-1274~~

Best regards, Eugene

[ Permalink | « Hide ]

Dmitry Yemanov added a comment - 08/Dec/10 10:57 AM

Backported into v2.5.1 and v2.1.4.