Fawn icon indicating copy to clipboard operation
Fawn copied to clipboard

Transactions for MongoDB (See the README)

Results 34 Fawn issues
Sort by recently updated
recently updated
newest added

Fawn is not working well with the new version of Mongoose (6.0.4). Getting error when using "Fawn.init(mongoose)". The new version of Mongoose implemented severals changes.

It says invalid mongodb uri and it should start with mongodb:// only MongoDB Atlas has provided mongodb+srv:// uri string. That's why getting error

Collection.update function is deprecated by mongoose which is causing trouble to update multiple records. Now using Collection.updateMany for updating records in mongoDB.

In had this problem in the production mode Invalid mongodb uri \"mongodb+srv://[email protected]/sample_mflix?retryWrites=true&w=majority\". Must begin with \"mongodb://\"" It seems to me that mongdb packages is to old, to use this tipe...

Hello, Emmanuel, I am Kayode, a came across this library a few months ago, I was fascinated by the functionality. Kudos. I took my time to read more about this...

There's an issue with initializing Fawn in mongoose ^6.0.5. This comes from the isMongoose function. the `modelSchemas` object of the mongoose instance has been replaced with `Schema ` from the...

I'm working on an application where i have to use 3 different database on 3 different cluster. Is there any way to use fawn to implement transaction on different database...

Could you please update to resolve this? Moderate Prototype Pollution Package mpath Patched in >=0.5.1 Dependency of fawn Path fawn > mongoose > mpath More info https://npmjs.com/advisories/779 High Denial of...

Bumps [mongoose](https://github.com/Automattic/mongoose) from 4.12.3 to 5.7.5. Changelog Sourced from mongoose's changelog. 5.7.5 / 2019-10-14 fix(query): delete top-level _bsontype property in queries to prevent silent empty queries #8222 fix(update): handle subdocument...

dependencies

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: > DeprecationWarning: collection.update is deprecated. Use updateOne,...

enhancement
priority: high