-
Notifications
You must be signed in to change notification settings - Fork 61
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
SQL2 queries need to quote searches on integer fields with SQLite #206
Comments
Note for Jackrabbit its the other way around. |
so the xpath queries make all numbers strings? maybe we need to build that into our query converter, to but quotes around all literals even when they are numeric. if the semantics of |
it seems indeed that the semantics of |
no .. imho we can now do this much easier since we have a separate column for the numeric values |
@lsmith77 any chance you could fix this? this is one of the few issues left in milestone 1.2... |
well I had a fix .. the issue is that I was unable to demonstrate the problem in a test.= |
so, what do we do? drop the issue, postpone it or apply your fix if we can also prove that it does not do any harm? |
@lsmith77 @dbu i have a similar failure in sulu. We query for tags which are saved as an integer array in a property. we can filter (in a sql2 statement where) with tags = 1 or tags = 2. which works very well as long as only one tag is assigned to a page. when we assign two tags (1, 2) on a page and trying to filter for the first tag (1) we get the right result and we are happy ... but when we filter for the second tag (2) then we dont get the page ... when we reverse the assignment and write (2,1) it works for the tag 2 but not for tag 1 ... i have talked to @dantleech this morning and he said i should place it into apostrophes and everything works fine! I will test it for jackrabbit but i think it is not a good solution, or is it this? |
ok .. could be related. if you can manage to come up with a test case, then I am sure we can fix it. |
@dantleech have found the issue and it is not related to this PR ... thanks! |
@lsmith77 do we consider this a blocker for 1.2? |
no .. I do not consider this a blocker .. at least it has only popped up as an issue in the benchmark. nobody else so far seems to have run into this. |
The following node
Will not be found with this query:
But it will be found with:
The text was updated successfully, but these errors were encountered: