Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

accent ignoring collation for unicode [CORE824] #1211

Closed
firebird-automations opened this issue Dec 3, 2003 · 6 comments
Closed

accent ignoring collation for unicode [CORE824] #1211

firebird-automations opened this issue Dec 3, 2003 · 6 comments
Assignees
@asfernandes
Labels
component: charsets/collation fix-version: 2.5 Alpha 1 priority: major type: new feature

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: seesink (seesink)

Is related to QA296

SFID: 853354#⁠
Submitted By: seesink

Hello,

I am trying to do a query like

SELECT name FROM artist WHERE name LIKE '%BJORK%'

And trying to get BJ??RK as a result. Note the accent.

(And results like BJ??RK, BJORK etc. would also be valid)

If I am not mistaken I would need a collation for this,
but the closest thing I found is:

http://www.brookstonesystems.com

Which is nice, but not for linux and no unicode support.

Am I right that this would need a unicode NOACCENT
collation? If so this is my feature request.

Workarounds for the problem are highly aprecciated. Are
there other collations / charsets in firebird which do this?

Cheers,
Remco Seesink

P.S. NOCASE would be nice too, but workaround with
UPPER works fine.

Commits: 840ff6f a4097d0 9ffe4b1
@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2004-06-25 01:42
Sender: raseesink
Logged In: YES
user_id=669582

We solved this by filling a separate wordlist without accents which was
done mainly for speed with search and solves the accent problem in the
same time.

A word list can be searched by index using START WITH "BJORK"
instead of LIKE "%BJORK%". It is not the same but in our problem set
it generates even better result as you get less false (semantic) positives.
Disadvantage is duplicating data and risk getting out of sync.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10848 ] => Firebird [ 15264 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

We have now UNICODE_CI and UNICODE_CI_AI.
UNICODE_AI (case-sensitive / accent-insensitive) still not present.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

Development: Finished

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is related to QA296 [ QA296 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pmakowski

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@asfernandes asfernandes

Labels
component: charsets/collation fix-version: 2.5 Alpha 1 priority: major type: new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@asfernandes @firebird-automations