avoiding identity columns is gonna be kinda difficult at this point. the app is already in production, and i dont see a way to easily change out the id columns on all the existing tables. i suppose sync would rather have a guid for a row key?
i guess so, according to
http://msdn.microsoft.com/en-us/library/bb726011.aspx. This would have been helpful to know when i wrote the first version of this app months ago. i had no idea at the time i would be needing to write for occasionally-connected clients.
hmmm......well i may have to be inventive for this thing. once i set the id seed to 1, it started autonumbering from 1 (even though i have 7800+ records now).
so here is my new solution:
i will connect to my server with a download-only data-caching scenario. when new records are added locally, they will be < 4000 (server equipment id numbering starts at 4500). so i now know anything less than that is local to that
client. when connection is available, i will query my local table for anything less than 4000, and insert those records into the server's table (using server auto-numbering). ). rinse and repeat until there is nothing under 4000.
then, after everything is happy, sync a fresh copy to the client.
also by doing this, i no longer need to worry about conflcts, since each local db maintains it's own set of stuff <4000 until the next sync.
seem reasonable?
~george
