Your Meteor.methods must be on both server and client for the simulation to work. No clientside method, no stub.
You don’t have to worry at all about update occuring in multiple times. The only update that actually matters is the one on the server. The one on the client is only for the user’s convenience.
I was unaware you can do it with collectionId instead of {_id: collectionId). Can’t find it in Mongodb docs. Well, good to know.
So you mean that “update” method in a stub only updates local database?
And I have a next question.
I am also using observeChange.
In this case, when do observeChange related events occur?
When updating local database, or when updating server database?