You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replication in its current form does not support serial Number -ish ids. When a model is created on an offline client with a conflicting id created on the server loopback assumes that the models are the same.
Replication in its current form does not support serial Number -ish ids. When a model is created on an offline client with a conflicting id created on the server loopback assumes that the models are the same.
FWIW, it is possible to support serial Number ids using a modified hi-lo algorithm. However, that would require non-trivial implementation effort (about 5-8 story points).
Changes are being tracked with the _id (ObjectID) instead of the value of the id field ('myIdProperty'). This completely breaks replication.
Isn't this a problem affecting all apps using MongoDB with custom numeric id fields? Will updateOrCreate use the numeric id field or the generated _id field to decided whether the model is the same or not?
Activity
bajtos commentedon Jan 9, 2015
FWIW, it is possible to support serial Number ids using a modified hi-lo algorithm. However, that would require non-trivial implementation effort (about 5-8 story points).
A comment in #933
Isn't this a problem affecting all apps using MongoDB with custom numeric id fields? Will
updateOrCreateuse the numeric id field or the generated_idfield to decided whether the model is the same or not?ritch commentedon Feb 18, 2015
Technically this is not a bug... but if you do not use GUIDs you will run into them fairly quickly.