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
Query error message, nice to have #72
Labels
Comments
Agreed. In fact, it is giving you a useful message, you just can't see it :) {"error":"exception: invalid operator: $neq","status":400} |
Cool! I'll run it with Firebug moving forward :) |
No, I'll fix it. I just haven't gotten around to handling all of these cases yet :P |
This has been fixed in |
bobthecow
added a commit
that referenced
this issue
Feb 11, 2013
… including warning about invalid operators in search. Fixes #72
Thank you! |
No problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nicktacular commentedJan 9, 2013
If you make a mistake in your query that's still valid JSON but it's not valid Mongo query syntax, it would be nice to get an error instead of thinking you're waiting a long time for data. For example, the following is invalid but a tired coder may not notice:
It would be nice to send back a message saying it's invalid syntax.
(What I really meant was
{Status:{$ne:"Published"}}
).The text was updated successfully, but these errors were encountered: