Note that there are some explanatory texts on larger screens.

plurals
  1. POInt Autoincrementing Primary Key and GUID column
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COGenerally speaking, an auto-incrementing key will *not* collide; in fact, I'm not sure how to make it happen (since most definitions in SQL include a `Unique` constraint). You might get `duplicate key` errors, though. Why are you letting outside vendors dictate what your internal keys are? Accept a completed record from them, and generate the keys yourself. If you're running out of keys, increase the size of the column (to a long). You could generate a new GUID column, yes, but you'd likely still be generating the GUIDs anyways, so what would be the difference?
      singulars
    2. COWell because they would be in a disconnected environment i.e on mobile devices in which they have their own copy of a subset of their data and the ability to add records - if adding or updating records I would need a means to match up records - the reason for thinking about using the GUID for the matching and syncing process.
      singulars
    3. COI see where you are going with the 'accept completed record from them' although I still need a matching process - i.e. I need to give the client something back for the record - an ID (cant use an INT as it could collide - as i have 1,000s of potential clients all doing inserts on their own subset and sycning to central db (whilst at the same time the central db is also having inserts done directly on it )
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload