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

Query error message, nice to have #72

Closed
nicktacular opened this issue Jan 9, 2013 · 6 comments
Closed

Query error message, nice to have #72

nicktacular opened this issue Jan 9, 2013 · 6 comments
Labels

Comments

@nicktacular
Copy link

@nicktacular nicktacular commented Jan 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:

{Status:{$neq:"Published"}}

It would be nice to send back a message saying it's invalid syntax.

(What I really meant was {Status:{$ne:"Published"}}).

@bobthecow
Copy link
Owner

@bobthecow bobthecow commented Jan 10, 2013

Agreed. In fact, it is giving you a useful message, you just can't see it :)

{"error":"exception: invalid operator: $neq","status":400}
@nicktacular
Copy link
Author

@nicktacular nicktacular commented Jan 10, 2013

Cool! I'll run it with Firebug moving forward :)

@bobthecow
Copy link
Owner

@bobthecow bobthecow commented Jan 10, 2013

No, I'll fix it. I just haven't gotten around to handling all of these cases yet :P

@bobthecow
Copy link
Owner

@bobthecow bobthecow commented Jan 18, 2013

This has been fixed in develop, and it'll go out in the next release. Thanks for reporting it :)

@bobthecow bobthecow closed this Jan 18, 2013
bobthecow added a commit that referenced this issue Feb 11, 2013
… including warning about invalid operators in search.

Fixes #72
@nicktacular
Copy link
Author

@nicktacular nicktacular commented Feb 11, 2013

Thank you!

@bobthecow
Copy link
Owner

@bobthecow bobthecow commented Feb 11, 2013

No problem.

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.