Conflict when the app already contains a `Transactions` collection

When an app already defines a MongoDB collection named transactions, the developers are forced to change its name after installing the package. I think that the collection created by the package should be renamed to something that is not a plain dictionary word to avoid any conflict.

[JackAdams]

Yes, I believe you’re right. I’ll accept a PR and republish if there’s a solution for this.

On another note, if you’re using this package to deal with money type transactions, I’d have to warn against it. Using this package is a step up from no db transactions, but it’s not mature enough to have important data relying on its functionality.

I use it in a couple of production apps and, although it hasn’t let me down, I know that it’s no big deal if it ever does.

[saliksaly]

Thank you Yes, I’ve read your warning about using it in money treating apps. I want it for simpe purpose, for my own risk.