case insensitive ISSUE
See original GitHub issueHi
I have two collections named book and user. User has field name which is case insensitive. Book has a linked class user. OrientDB version (2.1.10 and latest 2.1.13)
When I use
SELECT * FROM user WHERE name LIKE "adam%"
I will get 1 record
{ name: 'Adam Smith' }
When I try to find all book with query
SELECT * FROM book WHERE user.name LIKE "adam%"
I will get 0 records.
But next query is working correctly
SELECT * FROM book WHERE user.name LIKE "Adam%"
I will get 1 book.
I guess that orientdb has a bug because it will forget to use case insensitive search.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Case sensitivity - Wikipedia
In computers, case sensitivity defines whether uppercase and lowercase letters are treated as distinct (case-sensitive) or equivalent (case-insensitive).
Read more >Adjust case sensitivity - WSL - Microsoft Learn
Case sensitivity determines whether uppercase (FOO.txt) and lowercase (foo.txt) letters are handled as distinct (case-sensitive) or equivalent ( ...
Read more >How can I fix case insensitive database to be case sensitive?
1. Discover the issue mysql> SELECT @@character_set_database, @@collation_database; · 2. Make a backup of your database · 3. Detect the conflicts ...
Read more >The Case For Case Insensitivity - Coding Horror
This is a problem with scripting languages in general. Case sensitivity just happens to be one of the many ways that programmers can...
Read more >Case insensitive issue - Confluence
The issue applies to values of an inherited string type, such as 'enum', 'identity' and strings with pattern (e.g. yang:date-and-time). In order ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @seeden
Thank you for reporting. I think this issue is related to the fact that the query is checking only the schema of the target class, so the CI on the linked class is not taken into consideration (it’s just a guess, I have to double check)
I’ll take a look at that asap
Thanks
Luigi
Hi @seeden
I just tried latest 2.1.16 and it seems to work fine… could you please provide a full test case or script to reproduce it?
Thanks
Luigi