Closed tcastelli closed 8 years ago
Yeah, sorry about this. This is #38 again. The rollback mechanism is broken. There's a fix coming out soon.
0.7.5 should fix both these issue. Just released on Atmosphere.
Thanks I'll check it asap! El 22/11/2015 11:18, "Brent Abrahams" notifications@github.com escribió:
0.7.5 should fix both these issue. Just released on Atmosphere.
— Reply to this email directly or view it on GitHub https://github.com/JackAdams/meteor-transactions/issues/40#issuecomment-158743311 .
This is fixed, right? I'll reopen it if it's not.
Hi there, I've just installed this package for a simple transaction, code is like this (i'm using collection2 package too)
However the callback of commit is never called and I get this feedback from logs
The worse part, is that after the rollback, the document in CollectionA is still inserted with the last update on it, Meteor.users keeps the update and CollectionC document is deleted, producing a non desirable state :(
Am I missing something?