Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is meteor-transactions fully compatible with Collection2? #61

Open
ayalpani opened this issue Sep 20, 2016 · 3 comments
Open

Is meteor-transactions fully compatible with Collection2? #61

ayalpani opened this issue Sep 20, 2016 · 3 comments

Comments

@ayalpani
Copy link

Hi Jack

I was wondering about meteor-transactions and collection2 compatibility as I read the documentation which states:

"This queue is created by monkey-patching the insert, update and remove methods of Mongo.Collection instances so that these db mutator calls are intercepted and not executed until this package has done its thing (much like aldeed:collection2)."

If both packes monkey patch, do they still work together smoothley?
Thanks!

@JackAdams
Copy link
Owner

Well ... I use them together in a production app, but no guarantees ....

The transactions package is designed to work with the simple-schema package, but you may run into the odd unexpected behavior.

If you do, let me know and I'll try to fix it.

On Sep 20, 2016, at 8:13 PM, ayalpani notifications@github.com wrote:

Hi Jack

I was wondering about meteor-transactions and collection2 compatibility as I read the documentation which states:

"This queue is created by monkey-patching the insert, update and remove methods of Mongo.Collection instances so that these db mutator calls are intercepted and not executed until this package has done its thing (much like aldeed:collection2)."

If both packes monkey patch, do they still work together smoothley?
Thanks!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@ayalpani
Copy link
Author

Thanks for your quick answer, Brent. I'll let you know if

On Tue, Sep 20, 2016 at 2:18 PM, Brent Abrahams notifications@github.com
wrote:

Well ... I use them together in a production app, but no guarantees ....

The transactions package is designed to work with the simple-schema
package, but you may run into the odd unexpected behavior.

If you do, let me know and I'll try to fix it.

On Sep 20, 2016, at 8:13 PM, ayalpani notifications@github.com wrote:

Hi Jack

I was wondering about meteor-transactions and collection2 compatibility
as I read the documentation which states:

"This queue is created by monkey-patching the insert, update and remove
methods of Mongo.Collection instances so that these db mutator calls are
intercepted and not executed until this package has done its thing (much
like aldeed:collection2)."

If both packes monkey patch, do they still work together smoothley?
Thanks!


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAk0K-gb92RcuPwYZhmSS32MV77iI5Y4ks5qr87-gaJpZM4KBjOA
.

@inromualdo
Copy link

I think it is not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants