-
Notifications
You must be signed in to change notification settings - Fork 261
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
Regular Expression Operator #27
Comments
Hello! I am very glad to hear that you like tiedot. Did you mean using regular expression to filter certain attribute in query result? For example, matching |
Yes, or more complex: /[AF]/ in document's "grade". The high and low performers. Or again, to do wildcard searching,such as
Since Go has a regexp package (http://golang.org/pkg/regexp/), I thought it would be pretty easy and would be nice addition the current eq, range, and set operations. In SQL I use wildcards a lot and noticed the absence in tiedot right away. |
Oh! I see. In that case, I am afraid that index scan cannot help much at this stage, regex filter can be applied in collection scan (which is still quite fast). |
So would it look something like this? q='{"re": "Go|Clojure", "in": ["Title"]}' to find every title with either "Go" or "Clojure" in the title. Thanks for considering, |
That sounds like a great idea, let's do it. |
Fixed in d76e5aa thanks to NoahShen |
Great! Don't forget to update the docs to show how to use it! On Thu, Nov 7, 2013 at 1:47 AM, Howard Guo notifications@github.com wrote:
|
will do |
Completed 9a5026a |
I'm new to document databases and I wondered whether regular expression support would be useful. You could always do this on the client side, but a large result set could be slow (large amount of data being returned to client over network connection).
If the regex was implemented on the server side, wouldn't that be more efficient?
I'm enjoying tiedot, thanks!
The text was updated successfully, but these errors were encountered: