meteor-persistent-minimongo2
meteor-persistent-minimongo2 copied to clipboard
Go offline -> reload browser -> update minimongo record -> go online -> update is overwritten by mongo record on server
These work: Go offline -> update minimongo record -> go online -> server mongo record is updated, good! Go offline -> reload browser -> minimongo records are persisted, good! Go offline -> reload browser -> update minimongo record -> reload browser -> minimongo records are updated, good!
These do not work: Go offline -> reload browser -> update minimongo record -> go online -> update is overwritten by mongo record on server, bad! Go offline -> reload browser -> update minimongo record -> reload browser -> minimongo records are updated, good! -> go online -> update is overwritten by mongo record on server, bad!
Seems like once you reload the browser, it forgot if something local is updated, and will always be overwritten by older record from the server later on when there's connection.
Any thought or update on this?
@netmobile My usecase is the same as yours. How did you manage to connect and sync server collections with local collections? Can you share some code?