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

filter is not a function #196

Closed
kagahd opened this issue Sep 14, 2018 · 1 comment
Closed

filter is not a function #196

kagahd opened this issue Sep 14, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@kagahd
Copy link

kagahd commented Sep 14, 2018

Classic findOne() works:

mongo-seometadata-01(mongos-3.4.15)[mongos] seo-metadata> db.oopmetadata.findOne()
{
  "_id": {
    "siteId": NumberLong("10"),
    "productId": NumberLong("3395201")
  },
  "index": false,
  "lastModified": ISODate("2018-09-14T12:22:12.070Z")
}

But filter() wont work:

mongo-seometadata-01(mongos-3.4.15)[mongos] seo-metadata> db.oopmetadata.filter()
2018-09-14T15:44:42.755+0200 E QUERY    [js] TypeError: db.oopmetadata.filter is not a function :
@(shell):1:1

My mongo shell is v4.0.0, perhaps that's the reason that something is incompatible with it.

@stennie stennie changed the title filter is not a funtion filter is not a function Aug 24, 2019
@stennie stennie added this to the 0.1.0 milestone Aug 24, 2019
stennie added a commit that referenced this issue Aug 24, 2019
@stennie stennie closed this as completed Aug 24, 2019
@stennie
Copy link
Collaborator

stennie commented Aug 24, 2019

Adding collection.filter() as an alias for collection.find() doesn't seem constructive. I'm not sure if this existed previously, but I've removed the mention from the README.

@stennie stennie self-assigned this Aug 25, 2019
stennie added a commit that referenced this issue Aug 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants