-
Notifications
You must be signed in to change notification settings - Fork 16
FIREFLY-59: Filtering fail when value contains semicolon #828
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
Conversation
- added ability to separate condition with 'and' or 'or'
Just tried it. Looks good. |
Definitely a good improvement using 'AND' 'OR' for conditions. This was something we wanted to add for some time. I see that the tooltip has been changed to reflect this new capability. Great job! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed that AND and OR filtering works as expected. Semicolon filters do not work as expected.
A couple of unrelated things:
- I couldn't query the NEOWISE-R Single Exposure DB. This is also a problem on ops, so I'll send IRSA a ticket.
- Putting a string in double quotes instead of single quotes has some weird consequences. Sometimes the string is ignored (is "blah" -> is NULL) and sometimes it tries to be parsed as is (= "blah" -> ='"blah"').
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was testing test case from FF-59 JIRA ticket for the dealing with semicolon in the UCD column of the
Gaia tap service table.
It works.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I played with it and it’s a great and helpful improvement! Also noticed updated test! Thanks also for updating the tooltip! Awesome!
Good to be merged.
ticket: https://jira.ipac.caltech.edu/browse/FIREFLY-59
test: https://irsawebdev9.ipac.caltech.edu/FIREFLY-59/firefly/firefly-dev.html
As reported, filtering fail when the value contains semicolon. Because we were using semicolon to separate conditions, this messes up the underlying query statement.
Instead of just fixing the problem, I went ahead and allow the conditions delimiter to be either
AND
orOR
. Although this added a useful requested feature, it also may require updates to our online help. Please coordinate with the appropriate people after merging.Sample conditions:
> 0 and < 50 or is NULL
< 0 or > 100
in ('m31', 'm41') or is NULL