Closed paranoico closed 4 weeks ago
are you using the latest ground db II ? (cause that doesn't use stubfence)
Yes, using latest GroundDB II.
Seems to be a Meteor issue not preserving ID Consistent Generation and, in the other hand, similar to this: https://github.com/meteor/meteor/issues/1285
And GroundDB preserves the doubled data because the second document has another ID. So we have made a workaround creating our own documents IDs. So far seems to be working.
Thanks.
Should be fixed now. If not, then please re-open.
Hello again @raix,
We have found another issue for us using MantraJS:
Meteor.status().connected
can allow us to prevent stub action, but seems that it does not change immediately when connection is lost.I have also found this https://groups.google.com/forum/#!topic/meteor-core/s3OLSWj7kvI and your package https://github.com/raix/stubfence but does not seem to solve our specific problem.
Is there anything else we could try?
Thanks in advance.