You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we recently stumbled over the fact that nodeattr does not allow queries involving UTF-8 encoded attribute values.
We have actually quite a lot of them but apparently never needed to use them in queries. Also, I haven't seen any
documentation that says attributes must be ASCII.
The problem seems to be the lex tokenizer that matches only ASCII characters.
While it's not really straightforward to teach flex about UTF-8, a relatively simple patch seems to do most of the work:
Hi,
we recently stumbled over the fact that nodeattr does not allow queries involving UTF-8 encoded attribute values.
We have actually quite a lot of them but apparently never needed to use them in queries. Also, I haven't seen any
documentation that says attributes must be ASCII.
The problem seems to be the lex tokenizer that matches only ASCII characters.
While it's not really straightforward to teach flex about UTF-8, a relatively simple patch seems to do most of the work:
Any chance to see something like that in the next releases ?
The text was updated successfully, but these errors were encountered: