Brent Abrahams

Managing the size of the tx.Transactions collection

2

The `transactions` collection in the database of my production app is 10x larger than the next largest collection (in terms of disk space). For this reason, I'm thinking of making...

Mongo 2-phase commit should be implemented

6

[The mongo 2-phase commit approach](http://docs.mongodb.org/manual/tutorial/perform-two-phase-commits/) can be implemented in this package. It will take some refactoring, but it will ensure better data integrity than the current naive/optimistic transaction model that...

On the Mongo console: ``` meteor:PRIMARY> db.users.findOne({_id:"ZqRoBNapiGcQTtTBT", nonExistentField: "nonExistentValue"}) null ``` Which is expected. But in the Meteor shell and in server side app code: ``` > Meteor.users.findOne({_id:"ZqRoBNapiGcQTtTBT", nonExistentField: "nonExistentValue"})...

type="number" turns everything into an integer value

2

What about using something like `parseFloat` instead of `parseInt`?

Taken from a comment by @rogchap in #25: I have all my collections created in a local package (which is shared across multiple meteor apps), therefore `dburles:mongo-collection-instances` (which is used...