Skip to content
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.

Case-sensitive issue in filter operation #358

Closed
ajewelbd opened this issue Nov 9, 2022 · 7 comments
Closed

Case-sensitive issue in filter operation #358

ajewelbd opened this issue Nov 9, 2022 · 7 comments

Comments

@ajewelbd
Copy link
Contributor

ajewelbd commented Nov 9, 2022

Hi,
We are facing case-sensitive issue while filter from ui5.
Suppose, a column value is stored as 'Flush'. If we filter from ui5 'Fl', then we get the data.
But if we write 'fl', we get no data.

Best regards.
Md. Ashraful Alam

@gregorwolf
Copy link
Contributor

Hi @ajewelbd,

to help finding a solution it would be great if you could create a pull request that shows your issue in a new test request that you add to:

tests/assets/cap-proj/rest-client-test/beers.http

To replicate the behaviour of your UI5 app it's the best to look at the Network tab in the developer tools.

Best Regards
Gregor

@ajewelbd
Copy link
Contributor Author

ajewelbd commented Nov 9, 2022

@gregorwolf
Copy link
Contributor

Have you tested if it works with sqlite?

@ajewelbd
Copy link
Contributor Author

ajewelbd commented Nov 9, 2022

Yah, It is properly working in SQLite, But, not in postgre.

@gregorwolf
Copy link
Contributor

Can you provide also the output when you run the cds-pg variant with:

export DEBUG=cds-pg

and when running with sqlite use:

export DEBUG=sqlite

@ajewelbd
Copy link
Contributor Author

ajewelbd commented Nov 9, 2022

Hi.

I think i found the issue. In postgre LIKE operator is case-sensitive.
But, if we use ILIKE then it is woks fine.

If I am not wrong, in cds-pg 'LIKE' operator is used.

Thanks.

@gregorwolf
Copy link
Contributor

Would be great if you can contribute the improvement via a pull request.

ajewelbd added a commit to schertech/cds-pg that referenced this issue Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants