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

Freetext search on product data yields unexpected results with unicode characters #240

Closed
AndreasKl opened this issue Jan 27, 2015 · 2 comments
Assignees
Labels
Milestone

Comments

@AndreasKl
Copy link

If a ProductProjectionSearch#withText for a german umlaut is executed the search does not include words with the umlaut in the result set.

This ticket is mostly for tracking purposes as this could be a backend issue.

@schleichardt schleichardt added this to the 1.0.0-M11 milestone Jan 28, 2015
@schleichardt schleichardt self-assigned this Jan 28, 2015
@schleichardt schleichardt modified the milestones: 1.0.0-M12, 1.0.0-M11 Feb 13, 2015
@schleichardt schleichardt modified the milestones: 1.0.0-M12, 1.0.0-M16 Mar 3, 2015
@schleichardt schleichardt modified the milestones: 1.0.0-M13, 1.0.0-M16 Mar 25, 2015
@schleichardt
Copy link
Contributor

I could reproduce and tried to make a workaround:

Copy this class in the right package in your codebase https://gist.github.com/schleichardt/d8b3a9e1f82776fa7403

Usage:

final SearchDsl<ProductProjection> underlying = 
    ProductProjectionSearch.of(ProductProjectionType.STAGED).withText(GERMAN, "öón");
final Search<ProductProjection> useThisForExecute = Bug240Workaround.of(underlying);

@schleichardt
Copy link
Contributor

Sorry, it is a bug inherited from the Play SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants