Skip to content
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

[Feature/Improvement] Generic "NOT"/Negation #114

Closed
danieldjewell opened this issue Sep 15, 2021 · 1 comment
Closed

[Feature/Improvement] Generic "NOT"/Negation #114

danieldjewell opened this issue Sep 15, 2021 · 1 comment

Comments

@danieldjewell
Copy link

I searched through the issues and couldn't find anything on this (but also searching issues for "not" turns up just about every issue...)

One notable thing missing is support for generic negation in WHERE clauses - yes, there are two specific NOT operators (notlike and notrx) and I suppose ne/!=... But one cannot use say WHERE NOT name = abc ... Granted, the same functionality is there (WHERE name != abc) ... but having the generic negation NOT would be nice. (It would also make the syntax of fselect closer to real SQL ... writing WHERE NAME NOT LIKE vs the custom notlike -- I'm 99.9% sure that all SQL variants support a generic NOT operator.)

I really do love this program and a huge part of the reason I like it is because I can quickly do searches without having to pull up man find to figure out which flag I need. But a huge part of that convenience is based on being as close to generic SQL as possible.

Just a thought :)

jhspetersson added a commit that referenced this issue Nov 8, 2021
@jhspetersson
Copy link
Owner

Thank you for this suggestion! Although there was a special hack for WHERE NAME NOT LIKE syntax, now generic NOT can be used as well. Rather close to the real SQL :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants