loadOneOrCreate() about camo HOT 3 CLOSED

So it looks like the atomicity is possible with MongoDB 2.4, so my only issue is how this would work with other backends (NeDB, Taffy, etc). I'm hesitant to add a call to Camo that wouldn't be supported by the other backends, which makes me lean towards making it an option in loadOne(). But then, like you mentioned, we may need to let the caller know if the document was just created. Hmm....

Maybe we'll just have to add the loadOneOrCreate() method to Camo and use a non-atomic operation in NeDB, Taffy, etc.

I might test some things out and think about this. Any other thoughts or suggestions are welcome.

from camo.

So I'm thinking the Camo API should more closely follow the Mongo API as that will be the most-used backend DB. Any other supported DBs will have to support the same Mongo functionality through the Camo interface client.

So, I'll be adding a loadOneAndUpdate() method, which can then be used for loadOneOrCreate() functionality. Still debating whether I should stick with load..() vs find...() though...

I should be able to get around to adding this within the next day or two.

from camo.

Okay, I added support for this via loadOneAndUpdate(). Just use the option {upsert: true} and it'll return a newly saved document if one didn't exist already. Let me know if you have any questions.

from camo.