Home/ Questions/Q 7279135
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T22:59:21+00:00

So I have a relatively simple system. A mobile client creates records in a

  • 0

So I have a relatively simple system. A mobile client creates records in a sqlite database that I would like to have synced to a remote SQL server (that is shared with other mobile clients). So when I create a new record in the phone’s sqlite table, I then push that change to my remote service through a RESTful API. The problem I’m having, is how do I order the primary keys so that there isn’t collisions in the data (i.e. a record in the phone has the same primary key as a completely different record on the server). What is the usual “best practice for referencing the record on the client, and for referencing the same record on the server?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You could use a GUID type of column for the primary key. SQL Server supports the type UNIQUEIDENTIFIER SQLite supports the type GUID as far as i know (otherwise your client app on the phone has to produce a GUID value). This should guarantee unique values on client and server.

    • 0