-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
where clause on text with back slash \ requires 4 back slashes !! #136
Comments
As you probably know, Regarding your
I'm not sure to understand this question. As you said, I gave some tips in
I'm very sorry but I didn't understand this part… If you have an example of what you mean? |
Hi, My data is stored with one and only one back slash as 'domain\abc', I have created another sample example to illustrate what i was saying. Please see below my test on chrome console showing two queries, the one with 4 slashes works whereas the one with two return 0 rows. Cheers, |
I'll have a look later this week (on Tuesday or Wednesday) |
I've just fixed it in v6.1.2 Thanks. |
Tested the fix in v6.1.2, It works. Thx. |
First, excellent work and keep up maintaining this project.
I encountered a weird problem where I have a text column with text like domain\abc
to make the where condition work, i had to encode the back slash twice like this !
where:"My_Field = 'domain\\\\abc'",
I am not sure if this is the default behavior or a bug, but i found on the documentation of the Add function the following:
note: A person must be provided as "-1;#email" (e.g. "-1;#[email protected]") OR NT login with double \ (eg "-1;#europe\\foo_bar") OR the user ID as a number
Is there a documentation that explains how the where works for different column types and wich operators can work with each column type. although the generated documentation is good enough, most of the time it is trial and error process. having also this documentation will make a better person.
Note: The editor for reporting the issue in github also shows two back slashes as one, so I had to double the number of slashes in the message to have the correct number shown.
Thx
The text was updated successfully, but these errors were encountered: