|
|
|
|
|
|
by evanspa
3186 days ago
|
|
|
You are right. The way I solved for this scenario is that when a record is first created on the device, a GUID is created for it (and stored using another column of course). When POSTing new records to the server for syncing, the server will check the GUID and see if the record already exists in its database, and if so, can ignore it (so the duplicate isn't written). But yes, you're right overall - full offline mode w/syncing, etc is a big pain :) |
|
|