Primary Key Best Practice

Discussion created by flightprofessor on Feb 9, 2018
Latest reply on Feb 19, 2018 by jormond

Some say ALWAYS "number field: auto-enter, serial number, increment by one, cannot override".

Others go with "Get (UUID)".

But some say Get (UUID) slows things down in large DBs.

So some say Get (UUID) with a custom function to turn the UUID into a number field so everything stays fast.


Ultimate Question I'm trying to get answered: What's the best, most bullet-proof, reliable, persistent Primary Key formation?


Other Questions:

Is UUID absolutely, always, persistently unique?

Is using a custom function to manipulate a UUID too clever by half? Could it lead to issues down the road?