Allow regexp on like/nlike operator #378
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@slnode test please |
1 similar comment
|
@slnode test please |
As a regexp string As a regexp literal As a regexp object
ssh24
force-pushed
the
feature/allow-regexp-on-like-operator
branch
from
ac67b30 to
3e24854
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Allow the user to specify the regexp on a
likeornlikeoperator in different forms other than just string and then letting our mongodb ORM creating the RegExp object. This feature shall allow the user to filter usinglikeandnlikeoperator using different forms of regexp:'^H.')/^H/)new RegExp(/^H/))connect to #151