{"action":"created","issue":{"url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/43","labels_url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/43/comments","events_url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/43/events","html_url":"https://github.com/Irrelon/ForerunnerDB/issues/43","id":78582924,"number":43,"title":"Find behaves differently from MongoDB","user":{"login":"joshq00","id":5642190,"avatar_url":"https://avatars.githubusercontent.com/u/5642190?v=3","gravatar_id":"","url":"https://api.github.com/users/joshq00","html_url":"https://github.com/joshq00","followers_url":"https://api.github.com/users/joshq00/followers","following_url":"https://api.github.com/users/joshq00/following{/other_user}","gists_url":"https://api.github.com/users/joshq00/gists{/gist_id}","starred_url":"https://api.github.com/users/joshq00/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshq00/subscriptions","organizations_url":"https://api.github.com/users/joshq00/orgs","repos_url":"https://api.github.com/users/joshq00/repos","events_url":"https://api.github.com/users/joshq00/events{/privacy}","received_events_url":"https://api.github.com/users/joshq00/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Irrelon/ForerunnerDB/labels/discussion","name":"discussion","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-20T16:00:51Z","updated_at":"2015-06-11T09:32:48Z","closed_at":null,"body":"Document:\r\n```json\r\n{ _id: 1,\r\n  author: { name: \"John\", email: \"abc@xyz.com\" },\r\n  comment: \".....\",\r\n  .....\r\n}\r\n```\r\n\r\nSearching for `author.name: \"John\"` should return record 1, but does not.\r\n\r\nOne has to search `author: { name: \"John\" }` which returns record 1.\r\n\r\nThis differs from mongo in that the first example would return record 1 and the second would not. Nested objects must fully match. Searching for nested properties uses \"author.name\" syntax."},"comment":{"url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/comments/111063578","html_url":"https://github.com/Irrelon/ForerunnerDB/issues/43#issuecomment-111063578","issue_url":"https://api.github.com/repos/Irrelon/ForerunnerDB/issues/43","id":111063578,"user":{"login":"kevteljeur","id":641297,"avatar_url":"https://avatars.githubusercontent.com/u/641297?v=3","gravatar_id":"","url":"https://api.github.com/users/kevteljeur","html_url":"https://github.com/kevteljeur","followers_url":"https://api.github.com/users/kevteljeur/followers","following_url":"https://api.github.com/users/kevteljeur/following{/other_user}","gists_url":"https://api.github.com/users/kevteljeur/gists{/gist_id}","starred_url":"https://api.github.com/users/kevteljeur/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevteljeur/subscriptions","organizations_url":"https://api.github.com/users/kevteljeur/orgs","repos_url":"https://api.github.com/users/kevteljeur/repos","events_url":"https://api.github.com/users/kevteljeur/events{/privacy}","received_events_url":"https://api.github.com/users/kevteljeur/received_events","type":"User","site_admin":false},"created_at":"2015-06-11T09:32:48Z","updated_at":"2015-06-11T09:32:48Z","body":"For what it's worth, I set about implementing Forerunner into  a project (to replace my own, horrendous in-memory query system) but then I discovered this difference with the query language through trial and error. It's true that other libraries do this and of course a precedent has been set by now for existing users, but: The MongoDB implementation is very specific, and this implementation shouldn't be called 'Mongo-like', because the expectation is that it will behave the same way (in fact, with regard to nesting and dot-notation, Forerunner behaves exactly the opposite to MongoDB).\r\n\r\nI appreciate that readme.md has been updated since I first arrived at it, but it isn't compatible with MongoDB queries, and that should be explicit. I do look forward to the point when it is, it does look like a promising library to use."}}