-
Notifications
You must be signed in to change notification settings - Fork 54
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
Deprecation warning on update() #63
Comments
Thanks for pointing that out. There's no quick fix unfortunately; I'll have to upgrade the project's version of mongoose. I'll try to do that within the next couple of weeks but transactions are now a part of the recent MongoDB version. Have you tried the native transactions? |
Thank you for the quick response, mate! Yes, I tried my hands at the native mongoose transaction implementation as outlined here. But turns out, MongoDB Atlas cloud hosting locks you down to MongoDB version 3.6.7 for all M0 users like me. And transactions only come with version 4 upwards. So I still depend on your work (it's a lifesaver). :) |
Would like to see this too 👍 |
Is there any way to achieve the |
Still getting this WARNING: Please help !, how to fix this ?? |
I'm using Fawn in a NodeJS project with mongoose 5.2.13. The implementation works absolutely fine, however, the
update()
function returns a deprecation warning:Is there any way I could just use the
findOneAndUpdate()
function as recommended by MongoDB docs, with fawn? I even have the useMongoose argument set to true:task.run({useMongoose: true})
Any tip will be great!
The text was updated successfully, but these errors were encountered: